maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-174) mvn release:prepare will not tag in subversion repository
Date Tue, 25 Nov 2014 20:32:11 GMT

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

Michael Osipov closed MRELEASE-174.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.

> mvn release:prepare will not tag in subversion repository
> ---------------------------------------------------------
>
>                 Key: MRELEASE-174
>                 URL: https://jira.codehaus.org/browse/MRELEASE-174
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>         Environment: linux ubuntu 
>            Reporter: Andrew
>            Priority: Minor
>
> The release plugin won't tag a version in subversion after performing release:prepare
-DdryRun=true. 
> We are currently using a Subversion 1.4 client and repository server. 
> Steps to reproduce :-
> mvn release:prepare -DdryRun=true
> mvn release:prepare  (I assume should tag at this point)
> No tag is created in repository.
> If however the following :-  mvn release:prepare -Dresume=false is run  after the release:prepare
the tag will be created as expected.
> The output from the mvn release:prepare was interesting, it appears that the  release:prepare
-DdryRun=true has already performed the release preparation even though its a dry run.
> andrew@andrew-dev:~/development/persistence-r1$ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Persistence library
> [INFO]    task-segment: [release:prepare] (aggregator-style)
> [INFO] ----------------------------------------------------------------------------
> [INFO] [release:prepare]
> [INFO] Release preparation already completed. You can now continue with release:perform,
or start again using the -Dresume=false flag
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Thu Nov 09 09:08:23 EST 2006
> [INFO] Final Memory: 5M/10M
> [INFO] ------------------------------------------------------------------------
> My guess is that the release:prepare -DdryRun=true
> shouldn't write  completedPhase=end-release to release.properties ?



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message