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] > >
