[
http://jira.codehaus.org/browse/MNG-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier closed MNG-3545.
--------------------------
Resolution: Fixed
Fix Version/s: 2.1-alpha-1
I added an integration test for this and it seems to be working correctly now.
> Option -P-profile overridden if profile is activebyDefault
> ----------------------------------------------------------
>
> Key: MNG-3545
> URL: http://jira.codehaus.org/browse/MNG-3545
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.9
> Reporter: David Bernhard
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 2.0.10, 2.1-alpha-1
>
> Attachments: maven-profile-bug.zip, MNG-3545-profiles.patch
>
>
> In maven 2.0.9, deactivating a profile "foo" that is declared and marked
> activeByDefault in the local POM does not work, as in
> DefaultProfileManager.java:227 all activeByDefault profiles are added if no
> profile is explicitly given ("-Pbar").
> In the attached zip, run
> mvn -P-foo help:active-profiles
> and note that foo *is* active.
> The patch fixes these issues by checking all default-activated profiles
> against the exclusions list when they are added "by default".
--
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