Farrukh,
A word of caution. Once a release artifact is downloaded into the
user's local repository, I do not believe it will be re-downloaded
without manual intervention. Thus you may end up with the original and
re-spon artifact scattered throughout your developers. Since the name
of the artifact will be the same, which one is a developer using?
So I suggest NOT re-spinning an release.
Paul Spencer
Farrukh Najmi wrote:
Dear colleagues,
Does maven-release-plugin easily support the re-spinning of a release.
Re-spinning means that one makes a bug fix and then creates a new
release using the same release # as the previous release.
Also, the previous releases tag is reused to tag the latest bits.
I feel this is a valid use case when a release was cut and perhaps even
deployed but not announced and a bug is found during testing of the
release.
TIA for your guidance on how best to meet this use case.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
