For the purposes of consistency, I agree that plugins used to do basic utility things should be part of the Apache project. I think all of these fall into that category. That would leave the very specific plugins to be on mojo where it's probably more acceptable to have only source because the audience is smaller. Although in general I think Mojo needs to be deploying at least snapshots of the projects.
-----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, January 12, 2006 7:56 AM To: Mojo Developers Subject: [mojo-dev] Bringing plugins to Apache Maven 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: - build helper - jxr report (jxr) - surefire report (surefire) - changes/jira/announcement report (issue stuff in sandbox) - changelog report (scm) What do others think? The other ones I'm tossing up: - taglist (generally useful report) - dependency-maven-plugin (sounds generally handy in eliminating a lot of small antrunning - would need to investigate it more). Cheers, Brett
