Nikola Milutinovic wrote:
I have a fairly complex Maven2 project, which is done the "Maven 2 way", meaning that
sub-projects are sub directories, 1, 2 or 3 levels down. So, there is one global parent POM for the
entire project and a "leaf project" can have at least one more parent POM in the chain.
The way I work in this environment is to checkout the "leaf" project I am going to work on into the
Eclipse workspace and I enable the dependencies on it. Prior to that I have checked out the entire project
and ran "clean install" on it. That way all dependencies will be in my local repository and they
are (or should be) visible on "Maven dependencies" container.
Now, building with "mvn" works like a charm.
Using older DEV version of m2clipse worked, too.
The latest STABLE release (the one with "Enable nested modules" option) is giving me
problems. It is not picking up dependencies from the parent POM. Consequently, they are not in
"Maven dependencies" node and my Eclipse is flashing red (cannot import ...) all over the
place.
If I manually add the "missing" dependencies to the "leaf" project's POM all is
well. But, of course, this is not proper.
Am I missing something really crucial here? Or is this a bug?
"enable nested modules" is a confusing name. this option enables
picking up dependencies from the nested modules and flatten them in the
current project. So, you clearly don't need this feature enabled on your
project.
See http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management
For the rest - please open a jira issue and attach sample project that
would allow us to reproduce this and that we could later include into
our test suite. We already have some test that cover scenario similar to
what you describing, but few more tests won't hurt. See some hints at
http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
