You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ondrej Zizka (JIRA)" <ji...@codehaus.org> on 2010/12/21 00:22:58 UTC

[jira] Commented: (MNG-4946) Let the order of profiles in `mvn -P...` determine their order in effective POM

    [ http://jira.codehaus.org/browse/MNG-4946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249202#action_249202 ] 

Ondrej Zizka commented on MNG-4946:
-----------------------------------

Currently, the resulting order is:

1. settings.xml - Auto-activated profiles (<activation/>), reverse definition order
2. settings.xml - CLI activated profiles, reverse definition order
3. pom.xml repos
4. parent pom repos

And adding auto-activated profile to -P does not change the result.

> Let the order of profiles in `mvn -P...` determine their order in effective POM
> -------------------------------------------------------------------------------
>
>                 Key: MNG-4946
>                 URL: http://jira.codehaus.org/browse/MNG-4946
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Artifacts and Repositories
>    Affects Versions: 2.2.1
>            Reporter: Ondrej Zizka
>
> Currently, the order of profile references on the command line does not affect the order in which they are merged to the effective POM.
> Easy test:
>   1) Create two profiles in settings-test.xml, say profA and profB
>   2) add a repository to each, say repoA, repoB
>   3) run `mvn -s settings-test.xml -PprofA,profB help:effective-pom`
>   4) run `mvn -s settings-test.xml -PprofB,profA help:effective-pom`
> You will see that the order of repositories is not affected by the order of profiles after -P.
> This behavior is not documented, AFAICT, so changing it shouldn't be considered as breaking backward compatibility.
> A possibility to determine the order in which profiles are applied would be a great improvement since it would allow changing the build dramatically just by slightly changing the command.

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