You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/16 22:40:27 UTC

[jira] [Closed] (MRELEASE-866) "successful" release:perform with dryRun=true should not invoke release:clean

     [ https://issues.apache.org/jira/browse/MRELEASE-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-866.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> "successful" release:perform with dryRun=true should not invoke release:clean
> -----------------------------------------------------------------------------
>
>                 Key: MRELEASE-866
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-866
>             Project: Maven Release Plugin
>          Issue Type: Wish
>          Components: clean, perform
>    Affects Versions: 2.4.2
>         Environment: maven-2.2.1
>            Reporter: Jürgen
>            Priority: Minor
>
> I recently upgraded maven-release-plugin version to 2.4.2 from 2.0
> I observed a change in the behaviour of release:perform together with dryRun (on a side-note, in 2.0 dryRun user property did not seem to have an effect on release:perform)
> basically:
> 1. dryRun=true release:prepare
> 2. dryRun=false release:prepare: generate tag+release info
> 3. dryRun=true (due to it being considered in 2.4.2) release:perform: no deployment into repository, BUT release:clean removes release info
> 4. dryRun=false release:perform: fails, lacks release info
> I know I should not do step #3, but I recommend not to execute release:clean after a "successful" release:perform with dryRun=true



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)