[
http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244572#action_244572
]
Benjamin Bentmann commented on MNG-4917:
----------------------------------------
No, as can be seen from the example POM I provided. You should also keep in
mind that your POM by design uses a profile that only Maven 3.0 properly
activates.
> 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
