[EMAIL PROTECTED] wrote:
it seems that the newest version of m2 has an bug in the workspace
depedency resolution.
The following occurs: I have one project with one or more nested
modules that is dependent from another project. For both projects I
have workspace resolution enabled. Both projects compile nicely via
Eclipse, Maven invoked in Eclipse via M2 and Maven via the command
shell. But If I try to execute a Junit Test-Case in the dependent
project the Test fails with a ClasNotFound-Exception.
If I disable the workspace resolution the test runs but only if i
invoked "mvn install" in advance of starting the test.
In the attachment of this mail I send you two projects to reproduce
this bug.
I am using Eclipse 3.4 and M2 in the newest version
0.9.5.20080627-1152. The bug also occurs in the current stable
version 0.9.4.20080603-0114. In version 0.9.3.20080421-2352 the
plugin behaves well.
After updating to 0.9.4 version you need to run "Maven / Update
Project Configuration" action on your Maven projects in Eclipse
workspace. That would reconfigure projects to the changed defaults as
described in release notes and New and Noteworthy [1] for 0.9.4 release.
regards,
Eugene
[1] http://docs.codehaus.org/display/M2ECLIPSE/New+and+Noteworthy
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
