What happens if you run maven->update_project twice? There is a bug or race condition of some sort in PDE that programmatic project classpath update unreliable, but nobody come forward to investigate and fix it yet.
-- Regards, Igor On 2013-01-15 3:13 PM, Tonny Madsen wrote:
I have made a sample project that illustrates the problem. You can find it here: https://github.com/tonnymadsen/tests in m2e.tests.classpath Just right-click the project -> Maven -> Update Project... and the .classpath will be reduced to..nothing. /Tonny On Tue, Jan 15, 2013 at 3:52 PM, Tonny Madsen <[email protected] <mailto:[email protected]>> wrote: m2e: 1.2.0.120903-1050 Tycho: 0.16.0 (but also tried with 0.17.0-SNAPSHOT) I will see if I can re-cut down to a small example as well. /Tonny On Tue, Jan 15, 2013 at 1:51 PM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: What m2e and m2e/tycho version do you use? Are you able to provide small standalone example to illustrate the problem? -- Regards, Igor On 2013-01-15 <tel:2013-01-15> 5:18 AM, Tonny Madsen wrote: I have a problem with a PDE project where Maven -> Update Project... seems to reset the .classpath of the project. Though this only seems to happen when the project includes a number of local jar files. My original .classpath looks as follows: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry exported="true" kind="lib" path="lib/commons-lang-2.2.__jar"/> <classpathentry exported="true" kind="lib" path="lib/commons-__configuration.jar"/> <classpathentry kind="con" path="org.eclipse.jdt.__launching.JRE_CONTAINER/org.__eclipse.jdt.internal.debug.ui.__launcher.StandardVMType/__JavaSE-1.6"/> <classpathentry kind="con" path="org.eclipse.pde.core.__requiredPlugins"/> <classpathentry kind="src" path="src/"/> <classpathentry kind="output" path="target/classes"/> </classpath> And the reset version is reduced to: <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="output" path="target/classes"/> </classpath> Which is a bit too limited :-) At the same time I get a dialog with the following error "lib/commons-configuration.jar [in ...] is not on the project's build path" (though I have no idea as which is the root cause)... No other project exhibit the same problem. Removing the two libraries, "solves" the problem. The MANIFEST.MF and build.properties files are both correct and not changed in the process. /Tonny -- Tonny Madsen My profiles: LinkedIn <http://www.linkedin.com/in/__tonnymadsen <http://www.linkedin.com/in/tonnymadsen>> Twitter <http://twitter.com/__tonnymadsen <http://twitter.com/tonnymadsen>> Blogger <http://blog.rcp-company.com/> SlideShare <http://www.slideshare.net/__nonty <http://www.slideshare.net/nonty>> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> -- Tonny Madsen My profiles: LinkedIn <http://www.linkedin.com/in/tonnymadsen> Twitter <http://twitter.com/tonnymadsen> Blogger <http://blog.rcp-company.com/> SlideShare <http://www.slideshare.net/nonty> -- Tonny Madsen My profiles: LinkedIn <http://www.linkedin.com/in/tonnymadsen> Twitter <http://twitter.com/tonnymadsen> Blogger <http://blog.rcp-company.com/> SlideShare <http://www.slideshare.net/nonty> _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
