Errors running builder 'Android Resource Manager' on ADT

Question

I am facing a problem when I try to create new android project in eclipse adt plugin tools.

ERROR/EXCEPTION::

Errors occurred during the build. Errors

Answer 1

In my case, the error was solved by changing the workspace folder permissions with chmod 777.

I am using Mac OS X and downloaded the ADT bundle for Mac.

Answer 2

Make sure your java path points to the java SDK bin directory.. make sure you have installed the latest JDK t be safe..

Answer 3

Switching to a new workspace worked for me.

File-> Switch Workspace.

Answer 4

I use maven to build and integrate android projects with jenkins/netbeans. For editing android resources, I often use Eclipse because of the ADT plugin and better android resources support.

Eclipse (Kepler) has serious problems when you import maven-based android projects. It expects the project.properties file in the root folder and will NOT generate it on its own no matter what. Example content:

# this file is needed by eclipse (adt plugin).
# Project target.
target=Google Inc.:Google APIs x86:19

Additionally, create a sym link called "gen" pointing to target/generated-sources/r if using maven to build the android project on the command line. That way, you should be able to do "File->Import...->Existing Android Project". You get an error message, but it didn't matter in my case.

Additional hints in case you have problems with m2e-android plugin:

• always check that the output folders for source dirs and resource dirs are correct.
• check that source dirs are set as source dirs (you usually get a corresponding warning)
• if resources from dependencies are not included in the final apk, check the filter settings for your resource dirs
• you may need to "import maven project from existing sources" before importing it as android project from existing sources.
• make sure dependencies are imported into the workspace and open and referenced (project props -> android -> add lib)
• eclipse adt does not support aar libs, use apklib instead

Answer 5

I faced same problem on my New Macbook Pro so I just Downloaded JDK and installed it and problem fixed.

Answer 6

• It can happen if you are changing the location of files that your eclipse project uses.

• In that case you can copy the files directly to your resources folder inside the workspace instead of linking them with "import"