[
https://jira.codehaus.org/browse/MRELEASE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315081#comment-315081
]
Robert Scholte commented on MRELEASE-410:
-----------------------------------------
I consider to close this as "won't fix", because the active profile resolution
has changed with MRELEASE-571 for Maven3: the plugin will only pass the
(de)activated profiles from the commandline.
> Allow specifying specific profiles to execute in the prepare mojo
> -----------------------------------------------------------------
>
> Key: MRELEASE-410
> URL: https://jira.codehaus.org/browse/MRELEASE-410
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0-beta-8
> Reporter: Vincent Massol
>
> Right now the mojo calls project.getActiveProfiles() and adds them
> automatically to the "arguments". So they come in addition to profiles passed
> with "-Darguments=-Pprofile1,profile2,etc".
> We would like to only execute the passed profiles. I propose to add a
> "releaseProfiles" configuration element (as for release:perform, except that
> releaseProfiles values don't seem to be taken into account for perform for
> some reason but that's another problem).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
