[ http://jira.codehaus.org/browse/MNG-2136?page=all ]
John Casey closed MNG-2136:
---------------------------
Resolution: Fixed
modified the calculation used in activating <activeByDefault/> profiles.
Was:
If ANY profile {embedded in POM, external} was activated by a means *other*
than <activeByDefault/>, then all <activeByDefault/> triggers were suppressed.
Is:
If a profile that's embedded in POM is activated by a means *other* than
<activeByDefault/>, then all <activeByDefault/> triggers are suppressed.
For example, if I have a profile in my settings.xml that injects a new
repository, and that profile is in my <activeProfiles/> section in the
settings.xml, it *cannot* influence whether or not an <activeByDefault/>
profile is triggered in a build that I run. This should keep such local
environmental factors from changing the build process.
*NOTE:* This represents a subtle change in behavior from < 2.0.3 releases.
However, I believe the nature of this change will make <activeByDefault/> usage
more intuitive, and fix behavior that would otherwise appear buggy.
> Active profile in profiles.xml prevents active profile in pom.xml to be
> triggered automatically
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-2136
> URL: http://jira.codehaus.org/browse/MNG-2136
> Project: Maven 2
> Type: Bug
> Components: POM
> Versions: 2.0.3
> Reporter: Vincent Massol
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.3
>
>
> If there's a profiles.xml with an active profile in it, then the active
> profile defined in the pom.xml is ignored and not triggered.
--
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
