Hi Norbert, First my mail wasn't about discussing the way plugins are referenced. I thought this had already been discussed and agreed (i.e. using project.xml and <dependencies>).
Then your solution doesn't handle plugin versions. One project may want to use such plugin in version 1.0 and another may want to use another version. Here's an example: the checkstyle plugin. One project is using checkstyle 2.4 and another one is using checkstyle 3.1. BTW, I don't know if plugin versions are supportede right now, i.e. if it is possible to have the same plugin loaded twice, but with different versions... -Vincent > -----Original Message----- > From: Norbert Pabiœ [mailto:[EMAIL PROTECTED] > Sent: 11 September 2003 17:06 > To: Maven Developers List > Subject: Re: Core plugins? > > Vincent Massol wrote: > > What we seem to need is a way to prevent folks having to enter 20 plugin > > dependencies in all their project.xml. These are the "core plugin". But > > these plugins do not have to be located in Maven nor do they need to be > > distributed with Maven. > > This is a little weird. > project.xml contains dependencies for code, for compiling, testing and > running (maybe with distinction among them in future). > Adding plugins to dependencies is artifical. > How about something like > maven plugin:install foo > - > D"maven.repo.remote=http://my.plugin.repository/maven,http://www.ibiblio.o > rg/maven" > > This is done once and it is independent from any project exactly the way > core plugins are installed now. > > -- > Norbert Pabiś > > > --------------------------------------------------------------------- > 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]
