maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-736) Add dryRun flag to release:perform
Date Fri, 09 Mar 2012 21:57:03 GMT

    [ 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

        

Mime
View raw message