CODEWITHSUNDEEP
androideclipseresourcessdk
Sandy
Sandy

Reputation: 2692

Problems building Android project after Eclipse and SDK update

I have just updated Eclipse, the Android SDK, and everything else that appeared updatable, via Eclipse's Help->Check for Updates and Window->Android SDK Manager.

My project consists of a main project and 2 library projects. One library project is the normal Android License library project. The other library project contains Java files that reference Android resources that it itself doesn't contain, but that are present in the main project (for example R.id.myPic is used in the library project, but is actually contained in the main project). I had no problem building and running the main project before the update.

For some reason now I cannot build the main project. The main project folder has a "subfolder" called "Library Projects", which contains a jar file for the Android Licensing, but does not show a jar for the second library project. I also have a red exclamation mark on the main project folder.

For some reason I cannot rebuild the library file together with the main project. I've tried Cleaning all projects, building one then the other, building all, restarting Eclipse, but no luck.

If I go to the project properties, then Java Build Path, then Libraries, it appears that the jar file for the library project is missing, but I cannot independently create a jar file for this since it uses resources from the main project.

This is what my problems tab says: The container 'Library Projects' references non existing library 'C:\AndroidDev\workspace\FlashcardsCommon\bin\flashcardscommon.jar' Type: Build Path Problem

Any ideas?

Thanks a lot!

Upvotes: 3

Views: 5631

Answers (1)

Jonathan Schneider
Jonathan Schneider

Reputation: 27757

See this thread:

http://code.google.com/p/android/issues/detail?id=21031

  1. It generally helps to go to Window -> Preferences -> General -> Workspace and check "Refresh automatically". Then try clean building your projects incrementally.
  2. You may also have to remove the source inclusions that represented your library dependencies manually. You will find that ADT 14 and 15 are very frustrating to work with when you have library projects. It requires frequent manual cleans of libraries AND their dependent projects to make changes to library projects effective.

Altogether, good effort by Google, but it's a bit buggy.

Another similar thread:

Cannot build library dependent project after update to ADT 14

Upvotes: 2

Related Questions