Brian, sorry for not replying sooner. Waaaaaay behind on mail.
Given the feedback on this thread, you can expect the vote will probably be favourable. I'm gathering things up now to propose the necessary votes. - Brett Brian E. Fox wrote: > I'd like to bump this back into current discussion. I'm nearing an > almost complete rewrite of dependency-maven-plugin complete with unit > tests etc. Before I go through the motions of updating everything on > mojo, I'd like to know where it will eventually end up. Now is a real > convienient time for me to finish the refactoring as an apache plugin > (merging with the current mojo code is going to be interesting if it > goes back to mojo, it would be much easier to import fresh). > > -----Original Message----- > From: Vincent Siveton [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 08, 2006 3:41 PM > To: Maven Developers List > Subject: Re: Bringing plugins to Apache Maven > > +1 for bringing and merging plugins. > > Vincent > > 2006/2/7, Brett Porter <[EMAIL PROTECTED]>: >> This is not a vote. +1's here are just "I've read and think it's all >> good", but generally I'm just looking for feedback on specific plugins > >> and decision points before taking this any further forward. >> >> Some of the plugins that wound up in mojo seem better suited to the >> main Apache project due to a) originally coming from there b) having >> the core libraries located there c) being essential to the day to day >> use of the project. >> >> These are the ones I'm thinking of: >> - jxr report (relates to jxr) >> - surefire report (relates to surefire) >> - changes/jira/announcement report (relates to issue stuff in sandbox) >> - changelog report (relates to scm) >> - dependency-maven-plugin (sounds generally handy in eliminating a lot > >> of small antrunning). >> >> The other ones I'm tossing up: >> - taglist (generally useful report, originally came from m1) >> >> I put out a call for opinions and while the relevant mojo people were >> in favour, some of the Maven developers were either on the fence or >> against it. However, I didn't really receive an answer to my responses > >> to those concerns. >> As a community we need to decide where we are going to develop >> individual plugins. As I understand it, mojo.codehaus.org was >> established to: >> - develop things that can't be entirely under the ASL. >> - avoid developing plugins that rotted and tied due to lack of >> community in m1 >> - give a place for individual plugin developers to start out but still > >> operate in the same way as the Maven community. >> >> It's always been my thought that plugins at maven.apache.org should be > >> those used by 80% of Maven users or essential to its operation, and >> those that relate to the Maven subprojects themselves. Also, plugins >> in like groups should be kept together. >> >> So, time to bring it here and get everyone's feedback again. If you >> already had objections, please voice them again if they are still a > concern. >> What do others think? Note that this would imply bringing in a couple >> of new committers, but they are people that have been generally > helpful. >> Cheers, >> Brett >> >> --------------------------------------------------------------------- >> 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] > > > > > --------------------------------------------------------------------- > 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]
