Jason,
Classpath behaviour introduced in 0.9.0 was inconsistent and
"surprising" (a bad thing), i.e. m2e appeared to allow custom classpath
entries in build/launch classpaths but it did not always honour them.
Making custom classpath entries work everywhere let m2e support
semi-legitimate usecases like running unit tests with different JDBC
drivers and was actually easier to implement compared to fully
suppressing custom classpath entries. Obviously, "easier to implement"
was the decisive factor :-).
There is no explicit way to "disable" custom classpath entries but you
can "Restore Default Entries" on launch configuration classpath tab or
"Update Source Folders" on Maven project to remove all custom entries.
Jason Harrop wrote:
Hi Eugene
Regarding honouring the Eclipse build path ...
On Fri, Mar 28, 2008 at 2:21 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
c_inconnu wrote:
I have the same problem with the new version of the plugin. I understand
why it is now done that way but I totally agree with Thomas: that should not
be mandatory.
We already implemented this in trunk and it will be included in the next
build.
This seems to be working nicely in 0.9.2 (thank you!) ie Eclipse is
again able to use projects and jars I have manually added via the
Eclipse Build Path dialog.
I was just wondering, is this behaviour configurable somewhere, or is
the behaviour now that the Eclipse build path is always honoured (in
Eclipse)? (Not that I want to change the behaviour, it is just that
I'm a bit surprised that you guys made this change, given the hard
line taken by JVZ earlier in this thread)
thanks
Jason
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
