[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888473#comment-15888473
]
Jesse Glick commented on MNG-4917:
----------------------------------
So {{activeByDefault}} does not mean what you would intuitively think it
means—that the profile is active unless disabled. Rather, it means it is active
only if Maven cannot find some other—probably unrelated—profile to activate.
Basically this mode is useless.
> Profile not active even though it has activeByDefault set to true
> -----------------------------------------------------------------
>
> Key: MNG-4917
> URL: https://issues.apache.org/jira/browse/MNG-4917
> Project: Maven
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 3.0
> Reporter: Benson Margulies
> Assignee: Benjamin Bentmann
> Attachments: pom.xml
>
>
> I've got a parent pom with a profile with
> <activeByDefault>true</activeByDefault>.
> You can retrieve it for yourself via git clone
> git://git.apache.org/webservices-xmlschema.git.
> The problem is the sourcecheck profile in the parent pom.
> running mvn -Psourcecheck works as expected, but running without the -P fails
> to activate the profile.
> the help plugin, I think, has separate problems in this area, or perhaps it's
> not supposed to look at -P?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
