Maven 2 & 3

Priority for profiles activated by property or -P unclear

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Cannot Reproduce
  • Affects Version/s: 2.0.9
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

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:

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

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.

  1. XML File
    pom.xml
    27/Jul/10 1:37 PM
    1 kB
    Benjamin Bentmann

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-2309 Profile activation order is random

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Improvement - An improvement or enhancement to an existing feature or task. MNG-4946 Let the order of profiles in `mvn -P...` determine their order in effective POM

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Hide
Permalink
Benjamin Bentmann added a comment -

Running mvn validate -P override on the attached POM yields:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Integration Test :: MNG-4741 - OVERRIDE

i.e. the property test used in the project name evalutes to OVERRIDE as you expect and it should (i.e. active profiles are injected in order of declaration, last in wins).

Since you mentioned Hudson, I can only suggest to double-check the unexpected behavior is not caused by Hudson's Maven integration. Using a stock Maven 2.0.9 distribution (and all later versions), I cannot reproduce the issue.

Show
Benjamin Bentmann added a comment - Running mvn validate -P override on the attached POM yields: [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Maven Integration Test :: MNG-4741 - OVERRIDE i.e. the property test used in the project name evalutes to OVERRIDE as you expect and it should (i.e. active profiles are injected in order of declaration, last in wins). Since you mentioned Hudson, I can only suggest to double-check the unexpected behavior is not caused by Hudson's Maven integration. Using a stock Maven 2.0.9 distribution (and all later versions), I cannot reproduce the issue.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Andreas Ebbert-Karroum
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: