Benjamin Bentmann wrote:
Dennis Lundberg wrote:
-1 because a serious bug has just been found in taglist-maven-plugin 2.1,
which is the version being used in the proposed parent release.
But I believe it's fair to assume that most people currently use this
plugin
version without being affected by the bug (otherwise the bug would have
been reported earlier). That is to say, if we halt a release of a parent
POM just because one of the proposed *default* versions is known to have
bugs, hm, how did we ever get out a parent ;-) ?
I forgot to mention that the bug only happens when aggregate is set to
true in the plugin's configuration. Seeing as we have a couple of
aggregated builds in mojo, I thought it would be best to wait for the fix.
Releasing parents can be a tricky thing, for the reasons you mention. I
guess it comes down to if there is a fix for the bug or not :-) But
quite often you get into the chicken-or-egg discussion, especially when
dealing with parents for plugins.
Anyway, releasing mojo:17 was not urgent, it just had summed up enough, so
I'm fine with cancelling the release and retrying after
taglist-maven-plugin:2.2.
Benjamin
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
