I think I didn't follow you, but if you didn't promote the release on
Nexus, the artifacts won't be released, so the current staging 2.5.0
won't be promoted.
So, you can drop the staging repo, remove the tag, fix your issue and
redo the release again.
If you already promoted the staging repo, I agree with you.
Regards
JB
On 06/23/2014 02:30 PM, Stuart McCulloch wrote:
On 23 Jun 2014, at 13:28, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
Hi Stuart,
No problem, but I don't see why to cancel the 2.5.0 release. When we cancel,
it's especially to remove the tag, and redo the release with the same version
number.
Do you really want a plugin version out there that doesn’t work for the basic
case? This would be a really bad experience for users who didn’t know that
2.5.0 was a bad release.
Regards
JB
On 06/23/2014 02:13 PM, Stuart McCulloch wrote:
Hi,
Mark found a bug in the staged maven-bundle-plugin 2.5.0 release, so I’ve
cancelled the release vote and fixed it in trunk.
I’m considering staging the next release as 2.5.1 rather than re-using 2.5.0
(and having to change the tag in svn, etc.) … any thoughts/preferences?
—
Cheers, Stuart
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
