On 29/01/2010, at 5:37 PM, Jason van Zyl wrote: > > On 2010-01-29, at 6:29 AM, Brett Porter wrote: > >> >> On 29/01/2010, at 4:26 PM, Jason van Zyl wrote: >> >>> -1 >> >> got a reason? :) >> > > We should endeavour to leave only the build time related plugins being locked > down. Things like the IDE generating plugins, the site stuff, and archetype > stuff should all be removed eventually and decoupled from the core entirely. > We're just making a bigger mess tying all this stuff together and trying to > maintain it as a functioning unit in lock step.
I'm not sure that's addressing the same concern - I know there are problems with, say, the site plugin, being too coupled into the core, but locking down versions is a bit of a different matter. Even then, I agree with what you've said, but it seems like archetype might be a worthy exception since it's the first thing many users hit and used regularly by established users, and it has bitten us before. Even today, Maven 3 regularly updates release versions of the plugin so as soon as something is in the wild it'll get picked up (this may be a bug though - I'll add that to JIRA). I'm not that tied to the idea, it was just a thought to avoid the potential problem that had been raised by a user. I'd hoped to hear a few other opinions either way... if no one else speaks up in favour I'll just close the issue as 'won't fix'. - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
