Now that the Eclipse Android code has been passed over to the AndMore project this hard coding of the output directory might be something that can be fixed.Actually i was not subscribed before so could not reply properly. Here is the story:
in m2e-android, we have to setup the JUnit test launcher classpath a little bit differently than simple java projects: * we have to add all platform-provided deps from our special container * use bin/classes instead of target/classes (this is due to the limitation of the Android Development Tool (ADT) plugin) We have problems with the second step. Although we can easily add the bin/classes folder, we do no remove target/classes which takes precedence, hence resulting in the issue. Igor suggested to use a classifierClassPathProvider to sort that out. With that, we can easily tell m2e to use the proper folder. Unfortunately i found a problem about that, which i tried to explain in my previous post. So basically it seems since we have no classifier (""), and both the default and our provider applies to the project, m2e cannot decide and uses a NOOP one. I hope the issue problem is clear now, if not, i try to add more details. Thanks for your help guys!
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people.
-- Paul Graham
|
