[
https://issues.apache.org/jira/browse/MRELEASE-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570668#comment-16570668
]
Robert Scholte commented on MRELEASE-1011:
------------------------------------------
I don't think your question is unique, but you should verify this with the
maintainers of the
[nexus-staging-maven-plugin|https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin].
I wonder if the maven-release-plugin fits in the continuous delivery process,
every commit is a potential release, so the tagging is overhead, the revision
is good enough. Though you must ensure a stable build, probably with several
maven-enforcer rules.
> 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)