Eclipse and Android and classpath: bin and target

I am using Eclipse 4.5 with m2e 1.6.1.20150625-2338, ADT 23.0.3.1327240, Android for Maven Eclipse 1.1.0 and 23.0.6.1720515. I have an Android project marked as "Is the library":

If I am running a Maven project | Update ... in the project, .classpath modified to contain the following:

 <classpathentry kind="output" path="target/classes"/> 

But then when I create the project, Eclipse changes this line to:

 <classpathentry kind="output" path="bin/classes"/> 

There seems to be a gap between what Eclipse thinks the classpath should be and what m2e thinks it should be. Obviously this harms my Subversion files.

Is there any tweak that allows m2e and Eclipse to agree on the classpath and not change it?

+8
android eclipse adt maven eclipse-adt
source share
2 answers

Maybe I was too wide for the first time, so here is what you can do:

Either lower your environment to 4.3 (this is annoying, and you complained about it.)

Or check in which version your project is installed. If it is installed in android 4.4, try setting the project version to 4.3 or the version the application worked on before you switch to 4.4 and it will work (if only something is different from your applications than my applications that are possible )

+2
source share

See this page. Incorrect build path only in certain workspaces (Android) .

This may help you solve this problem. "The project was not created because its build path is incomplete. The class file for java.lang.Object cannot be found. Correct the build path, then try to create this project" problem. -Aravindan.

+1
source share

All Articles