jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2 & 3
  • MNG-4088

[regression] settings.xml profiles are executed after project profiles

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Duplicate
  • Affects Version/s: 2.0.10
  • Fix Version/s: None
  • Component/s: Profiles
  • Labels:
    None
  • Environment:
    Windows, Linux
  • Complexity:
    Intermediate

Description

Examples like the one at http://www.sonatype.com/books/maven-book/reference/profiles-sect-tips-tricks.html do not work anymore.

The active profiles output is:
$ mvn help:active-profiles
Active Profiles for Project 'My Project':

The following profiles are active:

  • my-internal-profile (source: pom.xml)
  • my-external-profile (source: profiles.xml)
  • my-settings-profile (source: settings.xml)

instead of:
$ mvn help:active-profiles
Active Profiles for Project 'My Project':

The following profiles are active:

  • my-settings-profile (source: settings.xml)
  • my-external-profile (source: profiles.xml)
  • my-internal-profile (source: pom.xml)

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MNG-2276 profile activation by property doesn't work with properties defined in settings.

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

Bug - A problem which impairs or prevents the functions of the product. MNG-3614 settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Brett Porter added a comment - 22/Mar/09 11:49 PM

haven't yet confirmed

Show
Brett Porter added a comment - 22/Mar/09 11:49 PM haven't yet confirmed
Hide
Permalink
Benjamin Bentmann added a comment - 24/Mar/09 9:36 AM

AFAICT, the section in the guide actually never worked. Profile activation by property is currently limited to CLI properties and there is already an issue for activation from settings properties (MNG-2276). From my testing, this is no regression as simply no available Maven version ever supported this.

For the record: "execution" of a profile is a misleading term for profile handling. One would like the collection of properties from the settings.xml for activation of other profiles to happen first, but the injection of a settings profile into the POM should still happen last to ensure the user settings can override POM defaults.

Show
Benjamin Bentmann added a comment - 24/Mar/09 9:36 AM AFAICT, the section in the guide actually never worked. Profile activation by property is currently limited to CLI properties and there is already an issue for activation from settings properties (MNG-2276). From my testing, this is no regression as simply no available Maven version ever supported this. For the record: "execution" of a profile is a misleading term for profile handling. One would like the collection of properties from the settings.xml for activation of other profiles to happen first, but the injection of a settings profile into the POM should still happen last to ensure the user settings can override POM defaults.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Samuel Santos
Vote (0)
Watch (1)

Dates

  • Created:
    16/Mar/09 7:25 AM
    Updated:
    24/Mar/09 9:36 AM
    Resolved:
    24/Mar/09 9:36 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.