Community
Participate
Working Groups
Build Identifier: M20110210-1200 I have a Maven project in the workspace. I enable Maven Dependency management for another project (an Eclipse plugin that I want to make a child module of the parent project). When I edit the POM of the Eclipse plugin and select the parent project, if parent project is available in workspace, Relative Path should be filled with the relative path to the parent project. Reproducible: Always Steps to Reproduce: 1. Open the pom.xml of a module without a parent defined 2. Click on the icon on the parent section in the pom form editor 3. Select as parent a maven project that is available in the workspace 4. The Relative Path is not filled
http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=9790d5d92a1722d284263b90221f5a06b246a4a6 This gets the relative path for simple module creation. I've also fixed the hide nested modules for simple projects. Archetype module creation stumped me for the moment.
We don't appear to pass Archetyper an explicit parent, so perhaps it determines the parent by the location the new module is created. After speaking with Igor, we're using an older version of archetyper and newer versions aren't API compatible so I'll leave this with just fixing simple module creation.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
