[
http://jira.codehaus.org/browse/MNG-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4741.
----------------------------------
Resolution: Cannot Reproduce
Assignee: Benjamin Bentmann
> Priority for profiles activated by property or -P unclear
> ---------------------------------------------------------
>
> Key: MNG-4741
> URL: http://jira.codehaus.org/browse/MNG-4741
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.0.9
> Reporter: Andreas Ebbert-Karroum
> Assignee: Benjamin Bentmann
> Priority: Minor
> Attachments: pom.xml
>
>
> I could not find the situation documented somewhere, but the current
> behaviour is against my excpectation, hence a low priority bug report. In my
> pom, I have two profiles. One is activated by the -P command line option, the
> other by an environment variable. In variation of the example in MNG-2309:
> {code:xml}
> <profile>
> <id>default</id>
> <activation>
> <property>
> <name>env.WORKSPACE</name>
> </property>
> </activation>
> <properties>
> <test>DEFAULT</test>
> </properties>
> </profile>
> <profile>
> <id>override</id>
> <properties>
> <test>OVERRIDE</test>
> </properties>
> </profile>
> {code}
> env.WORKSPACE is set by Hudson, when the build is executed. When Hudson runs
> "mvn -P override" I would expect test set to override. As I said, this is my
> expectation, and I don't know if it was a consious design decision to make
> the priority of profile activation differently.
--
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
