[ http://jira.codehaus.org/browse/MNG-1493?page=comments#action_70063 ] John Casey commented on MNG-1493: ---------------------------------
I was thinking I'd just allow a full specification of the relative pom-file path for modules, just like we allow the parent/relativePath to refer to a specific pom file location. It would actually improve the consistency of these path-based elements of the core POM (ie. not plugin configuration elements). > 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 > Priority: Minor > Fix For: 2.1 > > > 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
