You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Bernhard (JIRA)" <ji...@codehaus.org> on 2008/04/24 11:02:46 UTC
[jira] Commented: (MNG-3545) Option -P-profile overridden if
profile is activebyDefault
[ http://jira.codehaus.org/browse/MNG-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132450#action_132450 ]
David Bernhard commented on MNG-3545:
-------------------------------------
While making the patch for trunk : Is it intentional that the roles of + and - are swapped, i.e. *+foo* _deactivates_ foo yet -foo *activates* it?
> 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
> Priority: Minor
> Attachments: maven-profile-bug.zip
>
>
> 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