Kasper Sørensen wrote:
Anyways, the link you refered to helped me. I had to use "import ->
Other -> Materialize Maven projects". Then I pressed "Next" (without
adding any Maven artifacts to the former dialog) and selected the root
directory of my parent project as "Location" instead of "Use default
Workspace Location".
Sorry, I am not following. When you checkout "parent" project from the
ide or import it from local system you are offered list of all nested
projects from selected location. If you selected not to import those
nested projects (modules) at that time, you can always call Maven import
project from the popup menu on parent project Import... / General /
Maven projects.
Note that "Materialize" wizard can only checkout Maven projects that
already deployed into some indexed Maven repository. This wizard need to
know Maven coordinates for projects to import and it seem like there is
a bug that left "Next" enabled when there is no artifacts selected (can
someone please create jira issue for that?).
Even though this solves my problem I would like to propose a more user
friendly way of materializing maven projects based on modules of a
parent project. Ideally I think it should be available directly from
the right-click menu on parent projects.
Can you please be more specific?
Note that "Materialize" wizard is already available from shortcuts in
"Maven Indexes" view as well from any jars inside other projects (both
maven-managed and not).
Also, we have been planning to merge all 3 import wizards into one
(import local, checkout from scm and materialize), but haven't got time
for that just yet.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
