-1

My company gave me a 4 year old Android Project that I have to fix. I've been used to working with IntelliJ and Android Studio for a while now. At first sight I saw this was an eclipse project and I've tried numerous things to get this to work on Android Studio, more specifically like the following.

I'm also trying to integrate Gradle in this project. But even after trial and error I do not get the expected result that I normally get with my own projects, note the arrows I usually get with my other projects. Now it looks totally different.

Any help or tips on how to get this old project back on its feet is highly appreciated.

Edito
  • 3,030
  • 13
  • 35
  • 67

3 Answers3

1

This could help you a lot:

Migrating from Eclipse ADT

Another critical thing is that if you are a keyboard-oriented programmer, it will take some time to get used to Android Studio's shortcuts. Even though it has some eclipse shortcut support.

Which can be easily found in here:

Eclipse Shortcuts

Good luck.

Community
  • 1
  • 1
Tiago Dávila
  • 346
  • 1
  • 7
  • I followed all the instructions in the first link for 3 times now. And I missed 1 important sentence that saved my project, so may I add that it is extremely important to read the following line in the first link: Select the Eclipse ADT project folder with the AndroidManifest.xml file and click Ok. I selected the parent folder of my eclipse project which gave nasty results. – Edito May 16 '16 at 12:28
1

You can follow the following steps, no need to export the projcet as Gradle, Android Studio (AS) provides this by default,

Go to File menu and select New -> Import Project

next from the File browser select your Eclipse Project folder,

click Next in the subsequent steps and lastly Finish to successfully import the project

There may be some dependncies of your project but you can read the instructions provided by the Android Studio import dialogs and handle them,

ask further if you need help.

Satyen Udeshi
  • 3,223
  • 1
  • 19
  • 26
1

In the worst case scenario, you can always make a project by the same name, copy the sources (and resources) into their corresponding package, move the relevant stuff from the old AndroidManifest to the new, and add the external dependencies (such as that Google Play Lib for example) through Gradle itself.

If the project uses NDK, then you're gonna have a bad time though, because that requires setting up the Gradle experimental branch.

EpicPandaForce
  • 79,669
  • 27
  • 256
  • 428