Hi,
we are here in a complete different situation.
During the VOTE the artifacts are stored in a stage repository which can
simply being dropped (Which is the idea of those staged repository). The
only thing which is needed to be fixed is the SCM Tag (Git, SVN...).
This can be done....
If we would have found the problem after they have been cleared and
released than it would be impossible to remove them from Central.
Furthermore the release area is a Subversion repository which can be
changed and it's documented according to the nature of SVN itself.
On 12/13/14 11:50 PM, Michael Osipov wrote:
Am 2014-12-13 um 23:46 schrieb Paul Benedict:
I can see your point. However, I don't think it's all that unusual for
people to see skipped versions during upgrading anymore. For example,
when
a security issue is found in a GA product, the affected version is
instantly pulled from distribution sites and a new version is published.
You cannot remove anything from Central, so even your broken GA will
remain there for ever.
How do you intend to avoid that?
Michael
Kind Regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
