I’ve got an android project and an android library project (my own) it depends on. I’m using maven, including maven-android-plugin, for the automated build, and Eclipse as my IDE, with m2eclipse and m2e-android to bridge the two.
For the most part, it’s working fine: I can do a maven build from the command line, and also build from Eclipse.
However, I semi-regularly get a build error in Eclipse for the main android app project that says “Project configuration is not up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix.”. When I do that, it seems to mess up the relative path from the app to the library project in the app’s project.properties file. Specifically, the relative path to the library project changes from the correct one to one that reflects the relative position of the projects in the Eclipse workspace.
Example: the disk layout looks like this:
/libs
— /my-lib
/apps
— /my-app
Thus the correct relative path from my-app to my-lib is ../../libs/my-lib.
However, in my Eclipse workspace, my-app and my-lib are siblings, and when I do Maven-Update project, it updates project.properties such that the relative path to my-lib (i.e “android.library.reference.1=”) becomes “../my-lib”.
As a result, in Eclipse, I get compilation errors for all the references in the main app to symbols in the library project. If I then go to the Android properties dialog in Eclipse, in the bottom section where library projects are listed, my library project has a red X next to it. If I remove it and add it back, thus correcting the relative path in project.properties, then everything is fine again.
This is kind of a nuisance. Any idea how to address it? Note: although the changes to the relative path I described are correct, it is only a theory that this is related to the relative position of the projects in the Eclipse workspace — that could be a coincidence.
This is a known issue and is being currently worked on:
https://github.com/rgladwell/m2e-android/issues/76