Go for it. I'm going to help retire them, after that it's fair game. So if you, and the folks who might want to work on it, are cool with that then take it over there.
My only concern is that we don't claim to support plugins that we have no real intention of supporting. Having them in our SCM is an implicit claim to support them. Just letting them sit there hoping people contribute patches I don't think is good enough. So if you want to give the maven-eclipse-plugin a happy life at Mojo then just take it there. On Nov 1, 2010, at 6:28 PM, Jörg Schaible wrote: > Jason van Zyl wrote: > >> >> On Nov 1, 2010, at 3:04 PM, Arnaud Héritier wrote: >> >>> For the eclipse plugin, I think that just moving it to retired isn't a >>> good think because even if we are agree that this one is now really >>> difficult to maintain, this is always the preferred integration way with >>> eclipse in many corporate environments. >> >> I think once it's retired anyone has the option to pick it up and maintain >> it. I think all we're saying putting it in the retired area is that we >> don't have the resources to support said plugin. Folks can do what they >> like after that. > > Why don't you move it then straight away over to mojo ? > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- the course of true love never did run smooth ... -- Shakespeare
