[
http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138968#action_138968
]
Chris Maki commented on MRELEASE-356:
-------------------------------------
Will the release plugin still set the property -DperformRelease=true? In the
plugin documentation for the release goal, there is an optional parameter,
arguments, but it seems this is ignored by the release goal. If you take away
the release profile, please keep the performRelease=true property or make
arguments work :-)
Given this plugin definition:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-7</version>
<configuration>
<arguments>-Pprofile-name</arguments>
</configuration>
</plugin>
The release goal has this output:
[INFO] Executing: mvn deploy --no-plugin-updates -DperformRelease=true -f
pom.xml
Note there is no -Pprofile-name in the resulting mvn sub-command.
> depreate the automated release profile
> --------------------------------------
>
> Key: MRELEASE-356
> URL: http://jira.codehaus.org/browse/MRELEASE-356
> Project: Maven 2.x Release Plugin
> Issue Type: Task
> Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1,
> so the release plugin should pre-emptively start ensuring users do this
> themselves
--
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
