Holy crap! Where did this mammoth list come from? I audited all the plugins that had significant changes and all the releases are done. jnlp was the only one that didn't get done, and it now has. I was going to vote on a Maven 1.0 release today, except that I found that javadoc fails fairly regularly at work.
Please, let's keep this sane. I see no reason to do any more plugin releases for 1.0 except for javadoc to fix this bug which I'll do tonight. If we do all these, all the testing needs to be done all over again. I'm +0 to releasing any of these plugins, but -1 to including those releases in Maven 1.0. Happy to hear convincing arguments on a plugin-by-plugin basis though. - Brett Quoting Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi, > > I would like to release some plugins before the 1.0 release. All this > plugins fix some little bug, so with a release, we'll limit bug registration > on jira or on mailling list. > > ant : +1 > appserver : +0 > changes : +0 > changelog : +1 > checkstyle : +1 > clover : +0 > dist : +1 > ear : +1 > eclipse : +1 > faq : +1 > hibernate : +1 > j2ee : +0 > jar : +0 > java : +0 > jboss : +0 > jdiff : +0 > jetty : +0 > junit-report : +1 > multiproject : +0 > nsis : +1 > pdf : +1 > rar : +0 > scm : +1 > struts : +1 > tasklist : +0 > war : +1 > webserver : +1 > > Emmanuel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
