[MRELEASE-1011] Deploy without deleting local copy
- Dominant language
- Java
- Stars
- 128
- Forks
- 145
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 3
Description
**[Chris Hennick](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=pr0methean)** opened **[MRELEASE-1011](https://issues.apache.org/jira/browse/MRELEASE-1011?redirect=false)** and commented
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.
---
**Affects:** 2.5.3
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the deploy, close, and release goals described in the issue and compare the Maven release plugin 2.5.3 behavior with the linked BetterRandom commit. Done means the release can be uploaded without deleting the local copy until close and release have completed, with deletion performed separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100