Thomas Tardy wrote:
I updated from version 0.0.12 to 0.9.0 a few days ago and it looks to
that everything is working well. Therefore I think that the issue
described in the following is more a missunderstanding from my side
than a bug.
In eclipse you have the possibility to configure the classpath of a
launcher and this was working well with m2eclipse v0.0.12. Since I
updated the plugin to v0.9.0 the classpath of the launcher is always
being restored to the default when I launch it. Can anybody tell me
what I'm doing wrong respectively how to do the same thing with the
v0.9.0.
Thomas, your observations are correct, and what happens is that we
always use corresponding Maven-managed classpath for JUnit and Java app
launch configurations (test and runtime scope accordingly).
As you noticed, it is still possible to edit both buildpath and
runtime classpath using a standard Eclipse UI and it is confusing that
edited configuration is not being used. We haven't decided if we should
look if we can disable such editing in JDT UI if Maven dependency
management is enabled, or if we should use these changes at a price of
breaking command line Maven build.
Anyways, in a mean time you can add additional dependencies to the
pom.xml using test and runtime scopes, so they will be used by launch
configurations.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
