You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2010/11/26 14:30:18 UTC
[jira] Commented: (MNG-4917) Profile not active even though it has
activeByDefault set to true
[ http://jira.codehaus.org/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244569#action_244569 ]
Benson Margulies commented on MNG-4917:
---------------------------------------
New behavior in 3.0, right?
> 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