Levina, Irene wrote:
Maven multi-module project (nested modules) could have different
structures in Eclipse Workspace.
Such as:
* First scenario: Using multiple Eclipse projects:
Parent Project -> pom (packaging pom)
ModuleA Project -> pom(packaging jar,
inherits parent pom)
ModuleB Project -> pom (packaging jar,
inherits parent pom)
* Second scenario: Using single Eclipse project (project with
multiple src directories):
Project folder -> pom (packaging pom)
ModuleA Folder(parent of src/main/java)-> pom
(packaging jar, inherits parent pom)
ModuleB Folder( parent of src/main/java)-> pom
(packaging jar, inherits parent pom)
My questions are:
How idempotent multi-module support (such as would it work properly
with both scenarios listed above)?
Is there are any problem, issues with the second scenario?
What are the additional features (functionality) would be available
for Eclipse project if nested modules are enabled?
Irene, Import Maven Project wizard allows to chose if multi-module
project should be imported as a single project or as multiple Eclipse
projects (an Eclipse project per-module).
The major advantage of single project is that it less verbose and it
may work little better with some SVN plugins (for example, Sublipse is
little shaky when working with overlapping nested projects).
However, from the dependency resolution point of view, multi-project
setup allows us to be much closer to the Maven dependency resolution and
provide more accurate dependencies for each module. That is why we
recommend it as default choice.
So, all in all both these variants have their own pros and cons, so we
have our recommendation, but also allow user to tweak it.
I've added a note about this to the project wiki page at
http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
