Pretty sure you stepped into the realm of over-analysis with that one. I was just trying to isolate the list of categories to one's where plugins couldn't qualify for more than one. I'm not interested in running off into the matrix daisy-patch with you.
+1 for doing whatever you want. You've succeeded in losing my interest in contributing to an ideal solution. Kris On Sat, 2007-04-07 at 10:03 -0500, Eric Redmond wrote: > But this is a weakness of the plugin concept... a "plugin" is a > collection of "goals" which are undeniably functional units. Obviously > a plugin, being a collection, can be utterly incoherent. But this > isn't the standard that we promote. Most plugins have a primary > purpose - eg, maven-jar-plugin... which is to "jar", only secondarily > to "sign-jar". Grouping is not an exact science, but that tends the be > the way people conceive of them. If you want to get into the > nitty-gritty of grouping, we can create a matrix, grouping per-goal. I > doubt you'd find many supporters of that, however. > > Eric > > On 4/6/07, Kris Bravo <[EMAIL PROTECTED]> wrote: > > I disagree that reports are functionally distinct. Take for > example the > cobertura plugin - You can configure it to fail a build if > your test > code coverage is less than 70% for example. This has nothing > to do with > reporting, even though cobertura will produce a coverage > report as > well. > > In short, although plugins may have goals which create > reports, it > doesn't make their primary purpose reporting plugins. This > causes > ambiguity when trying to classify a plugin. > > Kris > > > On Fri, 2007-04-06 at 13:52 -0500, Eric Redmond wrote: > > > > > > On 4/6/07, Kris Bravo <[EMAIL PROTECTED]> > wrote: > > Jason, > > > > I vote we remove the "reporting" group from your > preliminary > > list and > > redistribute everthing under it into other > categories. Maybe > > this? > > > > +0 > > > > I won't veto it, but reports are functionally distinct from > other > > types of plugins... so distinct they have their own > lifecycle (site - > > fwiw) and configuration element in the POM. I prefer a > seperate > > group... I'm not against sub-groups, however. > > > > > > Testing > > * cobertura-maven-plugin > > > > Documentation > > * taglist-maven-plugin > > * docbook-maven-plugin > > > > Analysis > > * jdepend-maven-plugin > > * jdiff-maven-plugin > > * javancss-maven-plugin > > * rat-maven-plugin > > * clirr-maven-plugin > > > > > > > > On Thu, 2007-04-05 at 17:39 -0700, Jason Dillon > wrote: > > > Any ideas what the categories should be... and > which plugins > > go where? > > > > > > > > > I'm not super familiar with all of the plugins > hosted > > there... but > > > here is a stab: > > > > > > > > > Scripting > > > > > > > > > * groovy-maven-plugin > > > * jruby-maven-plugin > > > > > > > > > Generators/Compilers/Translators (needs a better > name, or > > split up) > > > > > > > > > * aspectj-maven-plugin > > > * castor-maven-plugin > > > * commons-attributes-maven-plugin > > > * hibernate3-maven-plugin > > > * idlj-maven-plugin > > > * javacc-maven-plugin > > > * jaxb2-maven-plugin > > > * jpox-maven-plugin > > > * jspc-maven-plugin > > > * native-maven-plugin > > > * retrotranslator-maven-plugin > > > * sablecc-maven-plugin > > > * smc-maven-plugin > > > * wsdl2java-maven-plugin > > > * xdoclet-maven-plugin > > > * xmlbeans-maven-plugin > > > > > > > > > Testing > > > > > > > > > * selenium-maven-plugin > > > * dbunit-maven-plugin > > > * findbugs-maven-plugin > > > > > > > > > App Server > > > > > > > > > * jboss-maven-plugin > > > * tomcat-maven-plugin > > > * weblogic-maven-plugin > > > > > > > > > IDE > > > > > > > > > * netbeans-freeform-maven-plugin > > > * nbm-maven-plugin > > > * ideauidesigner-maven-plugin > > > * pde-maven-plugin > > > > > > > > > Reporting > > > > > > > > > * cobertura-maven-plugin > > > * javancss-maven-plugin > > > * jdepend-maven-plugin > > > * jdiff-maven-plugin > > > * rat-maven-plugin > > > * taglist-maven-plugin > > > * docbook-maven-plugin > > > * clirr-maven-plugin > > > > > > > > > Tools > > > > > > > > > * axistools-maven-plugin > > > * build-helper-maven-plugin > > > * exec-maven-plugin > > > * keytool-maven-plugin > > > * minijar-maven-plugin > > > * native2ascii-maven-plugin > > > * sql-maven-plugin > > > * xml-maven-plugin > > > * webstart-maven-plugin > > > > > > > > > I might have missed a few... anyways, just a stab > at what > > > the categories could be. > > > > > > > > > Any comments? > > > > > > > > > --jason > > > > > > > > > > > > > > > On Apr 5, 2007, at 7:13 AM, Eric Redmond wrote: > > > > > > > > > > > > > > > On 4/4/07, Jason Dillon < [EMAIL PROTECTED]> > wrote: > > > > Can we re-arrange the site plugin list > (on this > > page http:// > > > > mojo.codehaus.org/) to group plugins by > > functionality > > > > instead of by > > > > release status? > > > > > > > > Like I'd like to see a "Language > Support" group > > or > > > > something, that > > > > has the groovy-maven-plugin and > > jruby-maven-plugin. > > > > > > > > I'd also like to see the latest release > version on > > the page, > > > > just > > > > like how the main maven plugins page > > > > ( http://maven.apache.org/ > > > > plugins/ ). > > > > > > > > I think that the main site index would > be a lot > > easier to > > > > grok if we > > > > updated it to follow the lead of the mvn > plugins > > page. > > > > > > > > Comments? > > > > > > > > +1 but don't involve the sandbox in that > grouping. > > > > > > > > > > > > Also, there is a lot of random garbage > in the site > > dav > > > > share, looks > > > > like some plugins were misconfigured at > some point > > and > > > > deployed site > > > > information in the wrong > directory. Looks like > > mostly > > > > appfuse and > > > > weblogic, though did find someother > stuff too. I > > think this > > > > should > > > > be cleaned up. > > > > > > > > --jason > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe from this list please > visit: > > > > > > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > > > > > > > -- > > > > Eric Redmond > > > > http://codehaus.org/~eredmond > > > > > > > > > > > > > > > > -- > > Eric Redmond > > http://codehaus.org/~eredmond > > > > > -- > Eric Redmond > http://codehaus.org/~eredmond
signature.asc
Description: This is a digitally signed message part
