I've been working through that list and I grabbed some of the serious artifact/repo issues as well as the highest voted issues from all groups for the .10 release. The plan most likely will be to fix the regressions and the most popular issues for 2.0.x but it is unlikely that all of those will get fixed; the edge cases and improvement issues will probably get bumped to 2.1 at some point. The 2.0.x branch should start to become very refined in scope of issues being fixed once 2.1 is closing in. Naturally people will still use 2.0.x for sometime so we'll be supporting it, but splitting the effort will only slow down the overall progress. (typical release management stuff yada yada)
The moral is to vote for the issues you most want fixed, and call out loudly regressions and blockers to updating as those are the priority. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Benedict Sent: Friday, March 07, 2008 8:11 PM To: Maven Users List Subject: Re: [POLL] Why are you not able to use the most recent maven release? There are about 110 bugs slated in the "2.0.x" release category. As I watch 2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not touched. My recommendation -- and hope -- is that someone could schedule a 2.0.11 and 2.0.12 based on 25 (swag) issues respectively from that big list. Those are the issues, it appears, that are long-standing and have been reported early. Paul On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox <[EMAIL PROTECTED]> > wrote: > > > If this is the case for you, please reply and state the version you're > > using and why (preferably referring to a Jira). We will use this > > information to prioritize issues for 2.0.10 and beyond. > > Some time after 2.0.5, Maven seems to have lost the ability to deal > with multiple repositories containing different versions of the same > plugin. > > For example: > * a 'third-party' repository with maven-whatever-plugin version 1.0 final > * a 'sandbox' repository with maven-whatever-plugin version 2.0-alpha-1 > > I think someone brought this up on the dev list recently as a problem > when trying to test a staged plugin release-- it would be the same > situation, with the latest release of the plugin in the 'central' repo > and the staged one in some other repo. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
