[ 
https://issues.apache.org/jira/browse/MRELEASE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570949#comment-16570949
 ] 

Chris Hennick commented on MRELEASE-1011:
-----------------------------------------

Per some discussion at 
[https://groups.google.com/a/glists.sonatype.com/forum/#!topic/nexus-users/KfZQ1QTpvgY|https://groups.google.com/a/glists.sonatype.com/forum/#!topic/nexus-users/KfZQ1QTpvgY.]
 I may be able to use 
[nexus-staging-maven-plugin|https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin]
 for the releases themselves, and maven-release-plugin only to set version 
numbers (although that does introduce the anomaly of having to alter a build in 
order to promote it, since the releases on Maven Central have to include the 
pom.xml).

> Deploy without deleting local copy
> ----------------------------------
>
>                 Key: MRELEASE-1011
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1011
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.5.3
>            Reporter: Chris Hennick
>            Priority: Major
>
> The `nexus-staging` plugin's `close` and `release` goals require that the 
> local copy of the release still exist, but the `deploy` goal cleans it up. 
> Thus, on my Maven Central project, 
> [https://github.com/Pr0methean/BetterRandom/commit/e3003a47d1dc85b42019612fff8d5431bae601a1]
>  (which seems to be the only way to automate the steps of closing and 
> releasing after uploading) fails. How can I perform the deletion separately 
> from the rest of the `deploy` goal so that it will succeed? This is blocking 
> my adoption of continuous delivery.



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

Reply via email to