Maven 2 & 3

profile deactivation has no affect

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.9
  • Fix Version/s: 2.0.10, 2.1.0-M1
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Brian looked at the source code, and it appears that deactivation of profiles should work. I'm using a profile that is active by default, and I want to override this.

The following command shows that deactivating my profile is not working. I tried this on 2.0.8 and 2.0.9

mvn help:active-profiles -P-oros

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO] ------------------------------------------------------------------------
[INFO] Building oros web component
[INFO] task-segment: [help:active-profiles] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [help:active-profiles]
[INFO]
Active Profiles for Project 'ca.athabascau.banner:web:war:1.1.23-SNAPSHOT':

The following profiles are active:

  • oros (source: settings.xml)
  • dev (source: settings.xml)
  • oros (source: settings.xml)
  • dev (source: settings.xml)

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Tue Apr 15 16:25:15 MDT 2008
[INFO] Final Memory: 3M/5M
[INFO] ------------------------------------------------------------------------

Issue Links

Activity

Hide
Paul Gier added a comment -

I'm closing this issue as a duplicate, and it will be fixed in MNG-3545. If this is incorrect, please re-open the issue.

Show
Paul Gier added a comment - I'm closing this issue as a duplicate, and it will be fixed in MNG-3545. If this is incorrect, please re-open the issue.
Hide
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

  • Assignee:
    Unassigned
    Reporter:
    Trenton
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: