Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342379

Summary:	Parent project selection should automatically fill relative path when parent is in workspace
Product:	z_Archived	Reporter:	Francisco Gortázar <patxi.gortazar>
Component:	m2e	Assignee:	Matthew Piggott <matthew>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	matthew, pascal
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Francisco Gortázar

2011-04-10 15:31:59 EDT

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

Comment 1 Matthew Piggott

2011-04-20 17:45:19 EDT

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.

Comment 2 Matthew Piggott

2011-04-27 13:13:51 EDT

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.

Comment 3 Denis Roy

2021-04-19 13:23:18 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/