Use Import Maven Project wizard [1] to import existing maven projects
into m2e workspace. With default import configuration this will create
separate eclipse project for parent project and individual modules. It
will also configure build classpath for all projects. See also [2].
[1] http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects
[2] http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management
--
Regards,
Igor
Yves Dessertine wrote:
Hi.
I have a problem with the dependencies of the children of a
multimodule Eclipse/maven project.
The parent has a packaging type "pom", and no dependency declared. Is
it good so far ?
Then, my modules (children) declare their own dependencies.
Everything is fine when compiling from command line. But in Eclipse,
all files are marked ascontaining errors : the dependencies aren't
resolved. The parent project has no dependencies. I declare the source
files manually on the parent project, tu make use of eclipse's
features.
What's the solution ? I also tried to declare new (eclipse) projects
for the children (by importing the folders as "Existing projects" from
within Eclipse, but I now have problems with SVN (subclipse). One
physical folder declared in two distinct Eclipse project makes
inconsistancies in Subclipse (bad handling).
Help :)
Yves
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
