Brett, I took wagon 1.0-beta3 released code from the tag and run unit tests on it and got failures. Do you have a theory how is that possible for a release?
regards, Eugene brettporter wrote: > > Sorry, but I still don't really get why you think a line of > development that is some time away from an alpha release needs to > worry more about the stability of a component that is already in place > for a point release. You could use beta-2, but I don't see the point > in that either. > > Only 2 things have cropped up in beta-3, and they've both been fixed > (WAGON-224, WAGON-225). There was one more that predated my changes, > also fixed in trunk and easily worked around in Maven (WAGON-237). > > Sure, it would probably have been better to rename 1.0-beta-2 as 1.0 > and release Wagon beta-3 as 1.1-beta-1. Hindsight is great. But plenty > of time was left for discussion, enough people voted for the release, > and I stand by it. Re-releasing something old as 1.0 when the others > are out would just be even more confusing. I don't really get what you > are trying to achieve that you can't do already. > -- View this message in context: http://www.nabble.com/Wagon-tp19132013p19193317.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]
