Thanks but I have a hard time understanding this to be the fundamental failure mode.
I have verified that for all build plugins (except site) we use fixed versions. (Although we give up automatic updates by doing this what we gain is repeatable builds where plugins used are always the same.) I missed site somehow, can that be causing release failures? There are no 3rd party dependencies in these projects these are all in-house components that build/release fine with 2.0.7. (Note that I have added more information to MNG-3351 regarding differences between beta-6 & beta-7 behavior with 2.0.8.) -Dave dhoffer wrote: > > We are at a critical point with our usage of maven. We cannot update to > 2.0.8 because 2.0.8 is broken with respect to the release plugin; RE > MNG-3351 (no releases are possible if using version ranges). > > However we need to upgrade to 2.0.8 because we now have large projects > that are tripping all over dependency/transitive/verson range bugs that > reportedly have been fixed recently. > > Can someone comment on the status of MNG-3351? We are at a blocking point > now where we cannot build anymore with maven. > > > -- View this message in context: http://www.nabble.com/2.0.8-and-release-plugin-bug-status-tp14966392s177p14995998.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
