[
http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4917.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
{noformat}
>mvn help:active-profiles -N
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building XmlSchema 2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-help-plugin:2.1.1:active-profiles (default-cli) @ xmlschema ---
[INFO]
Active Profiles for Project
'org.apache.ws.xmlschema:xmlschema:pom:2.0-SNAPSHOT':
The following profiles are active:
- maven-3 (source: pom)
{noformat}
And from [Introduction to Build
Profiles|http://maven.apache.org/guides/introduction/introduction-to-profiles.html]:
bq. This profile will automatically be active for all builds unless another
profile in the same pom is activated using one of the previously described
methods. All profiles that are active by default are automatically deactivated
when a profile in the pom is activated on the command line or through its
activation config.
In short, the profile "maven-3" disables "sourcecheck".
> Profile not active even though it has activeByDefault set to true
> -----------------------------------------------------------------
>
> Key: MNG-4917
> URL: http://jira.codehaus.org/browse/MNG-4917
> Project: Maven 2 & 3
> 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 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
