You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dominik Bartholdi (JIRA)" <ji...@codehaus.org> on 2012/02/08 19:23:02 UTC
[jira] (MRELEASE-736) add dryRun flag to release:prepare
Dominik Bartholdi created MRELEASE-736:
------------------------------------------
Summary: add dryRun flag to release:prepare
Key: MRELEASE-736
URL: https://jira.codehaus.org/browse/MRELEASE-736
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: perform
Affects Versions: 2.2.2
Environment: mvn 3.0.3
Reporter: Dominik Bartholdi
Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
I have the following use case:
Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
"-Dresume=false release:prepare release:perform"
the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Dominik Bartholdi (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293272#comment-293272 ]
Dominik Bartholdi commented on MRELEASE-736:
--------------------------------------------
for now I did implement a workaround on the jenkins plugin - but I still think this would be a good complement.
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Olivier Lamy
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291237#comment-291237 ]
Olivier Lamy commented on MRELEASE-736:
---------------------------------------
looks to be a simple skip of perform execution.
Others ?
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309807#comment-309807 ]
Jesse Glick commented on MRELEASE-736:
--------------------------------------
@Robert your comment of Mar 12 suggests that this Javadoc is quite wrong, and that it should say something like:
The {{deploy}} goal (or whatever is configured in {{goals}}) will _not_ be executed.
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309785#comment-309785 ]
Jesse Glick commented on MRELEASE-736:
--------------------------------------
Perhaps I am missing something but rev. 1299865 seems incomplete. At least according to http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#dryRun [t]he goals (by default at least {{deploy}}) will be executed against the current project. Is this just a matter of updating the Javadoc for {{PerformReleaseMojo.dryRun}}?
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Dominik Bartholdi (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293768#comment-293768 ]
Dominik Bartholdi commented on MRELEASE-736:
--------------------------------------------
I would just say what it normally would do...
But there is one more thing which I think would be a good thing in a dryRun: check whether the credentials work e.g. check if the build would at least be allowed to connect to the location where the site should be deployed to.
This is an annoying thing in most of the dryRun implementations, because a dryRun should test as many of the preconditions as possible but most do not test whether the configured connections would actually work. Specially in this case: if the release works fine, but the deploy of the site would fail - then a release job would be marked as failed - but in fact the artifact was released, but just not the site which leafs the user in an unsure state: "what should I do now? start over and create another version/release?"
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293304#comment-293304 ]
Olivier Lamy commented on MRELEASE-736:
---------------------------------------
@Robert +1
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293745#comment-293745 ]
Robert Scholte commented on MRELEASE-736:
-----------------------------------------
Fixed in [rev. 1299068|http://svn.apache.org/viewvc?rev=1299068&view=rev] for the plugin, the manager has already been prepared in previous commits.
There's only one thing which I'm not sure about: the perform-goals will be executed against the original project instead of the checked out project (that's good). But this also means that it will {{deploy}} (and often {{site-deploy}}) this SNAPSHOT-project. Should we try to catch these goals and replace it with {{verify}} and {{site}} respectively? Or add another option so you can choose? Prompt for it? Don't execute the goals, just say that it normally would? Or just leave it like this?
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309817#comment-309817 ]
Robert Scholte commented on MRELEASE-736:
-----------------------------------------
You're right, fixed in [r1390723|http://svn.apache.org/viewvc?rev=1390723&view=rev]
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MRELEASE-736:
-------------------------------------
Summary: Add dryRun flag to release:perform (was: add dryRun flag to release:prepare)
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-736.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Fixed in [rev. 1299865|http://svn.apache.org/viewvc?rev=1299865&view=rev].
We've decided that the plugin will skip the execution of the perform goals. The tests have already run during the {{prepare}} and since we don't check out the code it would run twice.
For the authentication and authorization to deploy the artifacts or the site we might need other release-phases or separate goal.
Most important: it's now possible to do a {{mvn release:prepare release:perform -Ddryrun}} at once.
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Dominik Bartholdi (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294031#comment-294031 ]
Dominik Bartholdi commented on MRELEASE-736:
--------------------------------------------
perfect, thanks Robert!
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293236#comment-293236 ]
Robert Scholte commented on MRELEASE-736:
-----------------------------------------
@olamy, almost but not quite. Every {{ReleasePhase}} must implement the execute and simulate methods. Right now there's no option to pass the dryRun option on a perform-method of the {{ReleaseManager}}, so it should be added. Actually, the number of arguments is growing and growing, so I think we should create a {{ReleasePerformRequest}} as an argument container.
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Olivier Lamy
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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
[jira] (MRELEASE-736) Add dryRun flag to release:perform
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=309800#comment-309800 ]
Robert Scholte commented on MRELEASE-736:
-----------------------------------------
Jesse, what would you expect? Any suggestion to improve the javadocs is appreciated.
> Add dryRun flag to release:perform
> ----------------------------------
>
> Key: MRELEASE-736
> URL: https://jira.codehaus.org/browse/MRELEASE-736
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.2.2
> Environment: mvn 3.0.3
> Reporter: Dominik Bartholdi
> Assignee: Robert Scholte
> Fix For: 2.3
>
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform" goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user to trigger a maven release. This plugin allows to define a commandline which should be executed in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a build and in this case it would just add "-DdryRun=true" to the configured arguments and thats it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to remove "release:perform" from the passed argument, which is relay ugly.
--
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