You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 00:51:13 UTC
[jira] Updated: (MNG-1493) Support in multiproject environment
modules with different named POMs
[ http://jira.codehaus.org/browse/MNG-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-1493:
------------------------------
Fix Version/s: (was: 2.1)
2.1-alpha-1
> Support in multiproject environment modules with different named POMs
> ---------------------------------------------------------------------
>
> Key: MNG-1493
> URL: http://jira.codehaus.org/browse/MNG-1493
> Project: Maven 2
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.0
> Reporter: Joerg Schaible
> Assignee: John Casey
> Priority: Minor
> Fix For: 2.1-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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira