I once did the work to put it into a separate plugin. The reason it was kept in the core project, was that the test framework depends on it (or on it's transitive dependency on maven).
Tom On Fri, May 18, 2012 at 11:36 AM, nicolas de loof <nicolas.del...@gmail.com>wrote: > afaik this is mostly for legacy reasons : > > maven project type was introduced as a core feature, and is still not > strictly isolated in a plugin, so it is packaged as a core plugin and must > be released with core > > not sure there is work in progress to get it better separated from core > and become a "classic" plugin > > > 2012/5/18 Ian Kemp <ian.k...@gmail.com> > >> Pretty much as the title says. I'm guessing because the "plugin" is >> actually a project type? > > >
