[
https://issues.apache.org/jira/browse/MNGSITE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516950#comment-14516950
]
Joerg Schaible commented on MNGSITE-222:
----------------------------------------
Keep it as it is. I made some tests and a profile activated by default was
never deactivated (in contrast to the statement in the [Sonatype
book|http://books.sonatype.com/mvnref-book/reference/profiles-sect-tips-tricks.html])
using the -P option from command line (tested with several Maven versions from
2.2.1 to 3.3.1).
> Incorrect statement regarding profiles activated with -P
> --------------------------------------------------------
>
> Key: MNGSITE-222
> URL: https://issues.apache.org/jira/browse/MNGSITE-222
> Project: Maven Project Web Site
> Issue Type: Bug
> Environment:
> http://maven.apache.org/guides/introduction/introduction-to-profiles.html
> Reporter: Sebb
> Assignee: Michael Osipov
>
> Website as above says:
> {quote}
> Profiles can be explicitly specified using the -P CLI option.
> This option takes an argument that is a comma-delimited list of profile-ids
> to use. When this option is specified, no profiles other than those specified
> in the option argument will be activated.
> {quote}
> The last sentence above is not true.
> As proof, try the following:
> {code}
> mvn -f <apache-parent-pom> help:active-profiles -Papache-release
> {code}
> The output is
> {code}
> Active Profiles for Project 'org.apache:apache:pom:16':
> The following profiles are active:
> - apache-release (source: org.apache:apache:16)
> - maven-3 (source: org.apache:apache:16)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
