[MNG-1493] Support in multiproject environment modules with different named POMs

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Fix Version/s: 2.0.9, 3.0-alpha-1
• Component/s: POM
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: Joerg Schaible
• Created: 10/Nov/05 10:41
• Updated: 21/Jul/17 08:34
• Resolved: 05/Feb/08 15:32

Description

Command line version of Maven 2 supports POMs with a different name using the -f option. Unfortunately such POMs cannot be used as modules, since the value of the module tag is defined as a directory to another pom.xml instead of a pathname to another POM. Only if the value is not already an existing file the value should be treated as directory with a present pom.xml file. Similar situation applies to the relativePath element of the parent tag.

This makes the generation of different artifacts from the same sources (with some modifications) much more easy. Currently you will have to put the POMs in separate directories and modify the sourec location into another module.

Issue Links

• is related to: MNGSITE-313 Add documentation for MNG-1493 (referencing POM file in <module>)
• supercedes: MNG-3150 Command line -f option should propagate to module poms.