[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886920#comment-17886920
]
Guillaume Nodet commented on MNG-4917:
--------------------------------------
It seems clearly documented at [https://maven.apache.org/pom.html] and
[https://github.com/apache/maven/blob/85f5dca4a61f2e0595c9cb7e7cbaa2de26a48e4a/api/maven-api-model/src/main/mdo/maven.mdo#L2758-L2760],
so I'm closing this bug.
> 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, 3.8.5
> Reporter: Benson Margulies
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-beta-5
>
> 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
(v8.20.10#820010)