maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2559) Module Selection From Command Line Argument Broken
Date Mon, 18 Jun 2007 00:16:57 GMT

    [ http://jira.codehaus.org/browse/MNG-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99795
] 

Brett Porter commented on MNG-2559:
-----------------------------------

you can also use -r

> Module Selection From Command Line Argument Broken
> --------------------------------------------------
>
>                 Key: MNG-2559
>                 URL: http://jira.codehaus.org/browse/MNG-2559
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 2.0.4
>         Environment: Linux 2.6.16-gentoo-r7 #3 SMP PREEMPT i686 Intel(R) Xeon(TM) CPU
3.40GHz GNU/Linux
> Java HotSpot(TM) Server VM (build 1.5.0_07-b03, mixed mode)
> Maven 2.0.4
>            Reporter: Gus Power
>             Fix For: Reviewed Pending Version Assignment
>
>
> Hi,
> I am unable to specify which modules to include in the reactor build from the command
line when invoking maven on the parent POM. Having searched around on Google I have seen references
to invoking maven using the following syntax: 'mvn -Dmodule=moduleName goal' but it does not
appear to have any effect. My solution is to define different module combinations in different
parent POM profiles but this is clunky and inflexible. This has been a key annoyance in setting
up different cruisecontrol configurations for our continuous build.
> Regards,
> Gus.

-- 
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

        

Mime
View raw message