>>>>> Igor Fedorenko <i...@ifedorenko.com>:
> Typical workspace filesystem directory structure looks like
> workspace/
> parentA/
> moduleA1/
> pom.xml
> moudleA1/
> pom.xml
> pom.xml
> parentB/
> ...
Hm... the directory structure I have used previously, using the
maven-eclipse-plugin, was something like this:
toplevel/
pom.xml
workspaceA/
pom.xml
moduleA1/
pom.xml
moudleA1/
pom.xml
pom.xml
workspaceB/
pom.xml
...
One would typically check out each workspace and work within that
workspace with eclipse. One couldn't edit the parent pom.xml directly
in eclipse then either, but since with m2e eclipse didn't offer anything
extra, compared to other text or XML editors, this wasn't much of an
issue.
> During project import m2e will logically (!) flatten nested directory
> structure and create workspace projects parentA, moduleA1, moduleA2,
> etc.
Hm... ok. Can you choose to have them logically nested in eclipse? I
think that would be clearer, maybe...?
(I can live with the current behaviour, though. Just a thought)
BTW Can m2e generate the structure you showed, with the physically
nested, but logically displayed side-by-side projects?
> m2e will properly link parentA/pom.xml to all module projects that use
> it as a parent, and all changes to the parent pom will be immediately
> applied to the modules.
Yup. Regular mvn behaviour for that directory structure.
> And you probably want to update to recently released m2e 1.2, you can
> find info how to install it on m2e download page [1]
Thanks! I will try that version out.
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
