Maven 2 & 3

Command line doesn't handle multiple -P correctly

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.7
  • Fix Version/s: 2.0.10, 2.1.0-M1
  • Component/s: Command Line
  • Labels:
    None
  • Number of attachments :
    1

Description

It is currently not possible to have more than one -P on the same command line. Only the first specified profile is considered.

So if you do

mvn -Pmain -Ptest

only the main profile will be taken into account.

This may sound enough but it's not when your maven call is wrapped into a batch file. Let's say you have a batch doing the compilation of a given module:

a.bat
-------------------------------------
mvn install -Pmymodule %*
-------------------------------------

and you want to pass a special integration tests profile you would do:

a.bat -Pintegration-tests

But that won't work since you are not allowed to have two -P.

To merge them in DOS shell is quite a pain in the ***....

Issue Links

This issue relates to:
MRELEASE-288 The plugin should merge the profiles on a release:perform Major Open
This issue depends upon:
MNG-3545 Option -P-profile overridden if profile is activebyDefault Minor Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

Do you want to activate more than one profile ?
If yes, look at mvn -h and you can close the issue :
...
P,-activate-profiles Comma-delimited list of profiles to activate
...

Show
Olivier Lamy added a comment - Do you want to activate more than one profile ? If yes, look at mvn -h and you can close the issue : ... P,-activate-profiles Comma-delimited list of profiles to activate ...
Hide
Permalink
Henri Tremblay added a comment -

No. I know I can do -Pmain,test.

What I need is two -P. One is directly in the batch file and one is passed by the user calling the batch file. The ones in the batch are the default for the script and the one added by the user are specific to a given batch call.

For example, I want to deploy on an application server. The deploy.bat contains a -Pdeploy to tell mvn it should deploy during the build. Then the user pass a -Pdev to tell that he wants to deploy on the dev platform.

That is not currently possible. And I don't want him to have to modify his settings.xml all the time.

Show
Henri Tremblay added a comment - No. I know I can do -Pmain,test. What I need is two -P. One is directly in the batch file and one is passed by the user calling the batch file. The ones in the batch are the default for the script and the one added by the user are specific to a given batch call. For example, I want to deploy on an application server. The deploy.bat contains a -Pdeploy to tell mvn it should deploy during the build. Then the user pass a -Pdev to tell that he wants to deploy on the dev platform. That is not currently possible. And I don't want him to have to modify his settings.xml all the time.
Hide
Permalink
Paul Gier added a comment -

Attaching a small patch to allow -P to be specified multiple times.

Show
Paul Gier added a comment - Attaching a small patch to allow -P to be specified multiple times.
Hide
Permalink
Henri Tremblay added a comment -

Nice! Thanks Paul

Show
Henri Tremblay added a comment - Nice! Thanks Paul
Hide
Permalink
Paul Gier added a comment -

This is now fixed in svn.

Show
Paul Gier added a comment - This is now fixed in svn.
Hide
Permalink
Paul Benedict added a comment -

It appears this patch also fixes MNG-3545

Show
Paul Benedict added a comment - It appears this patch also fixes MNG-3545
Hide
Permalink
John Casey added a comment -

Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

Show
John Casey added a comment - Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

People

Vote (1)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.