[
https://jira.codehaus.org/browse/MNG-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308389#comment-308389
]
Rollin Chen commented on MNG-1493:
----------------------------------
Here's an example for using alternative pom file in module
<modules>
<module>child/pom-jdk14.xml</module>
</modules>
> Support in multiproject environment modules with different named POMs
> ---------------------------------------------------------------------
>
> Key: MNG-1493
> URL: https://jira.codehaus.org/browse/MNG-1493
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.0
> Reporter: Joerg Schaible
> Assignee: John Casey
> Priority: Minor
> Fix For: 2.0.9, 3.0-alpha-1
>
> Attachments: DefaultMaven.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
