You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dave Syer (JIRA)" <ji...@codehaus.org> on 2008/12/12 12:59:19 UTC
[jira] Commented: (MNG-3150) Command line -f option should
propagate to module poms.
[ http://jira.codehaus.org/browse/MNG-3150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157835#action_157835 ]
Dave Syer commented on MNG-3150:
--------------------------------
I also think alternate poms in reactor builds would be very useful. In my case I need to build and deploy the same artifacts with different artifactIds to different repositories. I can't see how this is possible with profiles.
> Command line -f option should propagate to module poms.
> -------------------------------------------------------
>
> Key: MNG-3150
> URL: http://jira.codehaus.org/browse/MNG-3150
> Project: Maven 2
> Issue Type: Improvement
> Components: Command Line
> Reporter: Paul Gier
> Fix For: 3.0
>
> Attachments: MNG-3150-maven-core-r573613.patch
>
>
> I have a multi module project where I would like to have parrallel builds. The default pom.xml build would be using jdk1.5 or jdk6, and the parrallel build pom would be for creating retro compiled jdk14 artifacts. So the pom for this build would be "pom-jdk14.xml". I've explored other options such as using a classifier for the retro translated artifact, and using profiles to choose between jdk1.5 and jdk1.4 builds. But both of these have problems that I can't get around without a lot of difficulty.
> Using two separate poms works great for me for a single module project, but for a multi module project, I have no way to tell the modules to pick up a different pom.xml file.
> So for my multi module build I would like to be able to say
> mvn -f pom-jdk14.xml install
> And each module should then look for it's own pom-jdk14.xml. This could be made into the default behaviour of the "-f" option, or a new option could be introduced like "-fg" to use the other pom file globally across all the 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