[jira] [Commented] (MNG-4917) Profile not active even though it has activeByDefault set to true

["Joel Croteau (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329800#comment-16329800 ] 

Joel Croteau commented on MNG-4917:
-----------------------------------

This is an incredibly inane design choice. It makes `activeByDefault` very unpredictable, creating side effects in potentially totally unrelated areas of the POM, and has the potential to allow for some very hard to diagnose bugs in POM files. Please fix this or give us another option.

> 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
>            Priority: Major
>         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
(v7.6.3#76005)