My view is very simple: Let's move all plugins outside the core of Maven. However, ATM it is not done for the following reason:
- There is no mechanism for a project to tell which plugins it wants to use (and in what version). [Of course there would a list of default plugins with default versions when you download maven so that you don't need to specify the full list of plugins to use in each project]. Once we have this, I'll be the first to vote a big +1 to have each plugin as a separate project with its own lifecycle. -Vincent > -----Original Message----- > From: Michal Maczka [mailto:[EMAIL PROTECTED] > Sent: 24 June 2003 21:27 > To: Maven Developers List > Subject: Responsibility - was [RE: Simian Plugin (fully documented and > ready to use)\ > > Just wanted to express my opinion about new plugins. > > I don't think that we should add more plugins to maven, unless they are > really "core plugins". > > I think we have quite a lot of dead plugins and many broken plugins, > > I like more the idea of having this plugin elsewhere, so original plugin > authors > can take responsibility. > > Knowing Aslak's skills I have no doubt that Maven team can give him access > right > to CVS repository to let him maintain this plugin but I want to discuss > general policy regarding this subject. > > I think Aslak has a lot of experience with such problems from XDoclet > project. > > Simply any plugin which is based on external libraries is very sensitive > to > any changes in those > libraries. For example Hibernate, Torque, JBoss plugins will be broken > once > there is minor change in > those project. Keeping all plugin up to date in enormous work. > > From the other hand I feel that Maven should have a catalog of known > "foreign" plugins > ( in form both of web site, and machine readable file format (XML ?), so > any > plugin can be downloaded automatically) > > This will not only improve quality of code which is kept in our CVS > repository, but also > will increase the number of people which can actively work on plugins and > having cvs access rights, so > also plugin will be better. > > > What you think? > > Michal > > > -----Original Message----- > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 24, 2003 8:54 PM > > To: 'Maven Developers List' > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: RE: Simian Plugin (fully documented and ready to use) > > > > > > Hi Aslak, > > > > I love the idea of CPD/Simian. However, before we can commit anything > > here we would need agreement from redhillconsulting.com that we can put > > the simian jar in the Maven remote repository on ibiblio. > > > > If we don�t get this agreement, we could still store this plugin in the > > SF mavne-plugins project and users would need to download the simian jar > > and put it manually in their local repository. > > > > Thanks > > -Vincent > > > > > -----Original Message----- > > > From: Aslak Helles�y [mailto:[EMAIL PROTECTED] > > > Sent: 24 June 2003 13:58 > > > To: Maven Developers List > > > Cc: [EMAIL PROTECTED] > > > Subject: Simian Plugin (fully documented and ready to use) > > > > > > It seems Maven's JIRA still doesn't notify this list, so here I go... > > > > > > Simian (http://www.redhillconsulting.com.au/products/simian/index.html > > ) > > > is a great little tool that detects duplicate source code. Very much > > > like PMD's CPD (http://pmd.sourceforge.net/cpd.html), but a _lot_ > > faster. > > > > > > I have written a Maven report plugin for Simian that I'd like to > > > contribute to Maven. Have a look at some sample reports: > > > > > > http://www.picocontainer.org/simian-report.html > > > http://www.nanocontainer.org/simian-report.html > > > > > > It would be really nice to have the Simian Report included in the > > > standard reports, as it reveals refactoring candidates and is > > something > > > every sound project should have! > > > > > > It's all in JIRA: > > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-516 > > > > > > Cheers, > > > Aslak > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > ---------------------------------------------------------------------- > > Klikaj!!! I skorzystaj!!! >>> http://link.interia.pl/f1739 > > > > > > > > > > --------------------------------------------------------------------- > 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]
