> > 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. >
If you read the original discussions about this feature it was done for one reason only: To try and prevent people's builds from breaking just because we release a new core plugin. It was intentional that we only included plugins that are typically bound to lifecycles in addition to core ones (this includes enforcer, dependency, assembly etc). Help, eclipse, idea, archetype are in the same group to me and that is cli use only. Putting these things in the super pom was a crutch but the benefit of stable builds outweighted the downsides, for cli use plugins I don't see this benefit. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
