Yes, but you can just add the plugins to your project.xml.. I have done
this with plugins from maven-plugins.sf.net and torque plugin, and for me it
has worked quite well. A plugin is a dependency just like any other jar
file.
Also, this ensures that a user doesn't need version XXXX of Maven that came
with the set of plugins that you require for your project. From
scarab.tigris.org's project.xml:
<dependency>
<groupId>maven</groupId>
<artifactId>maven-tasks-plugin</artifactId>
<version>1.1.0</version>
<url>http://maven-plugins.sourceforge.net/maven-tasks-plugin/</url>
<type>plugin</type>
</dependency>
<dependency>
<groupId>maven</groupId>
<artifactId>maven-findbugs-plugin</artifactId>
<version>0.7.1</version>
<url>http://maven-plugins.sourceforge.net/maven-findbugs-plugin/</url>
<type>plugin</type>
</dependency>
Works great!
Eric Pugh
> -----Original Message-----
> From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
> Sent: Sunday, April 04, 2004 8:28 AM
> To: Maven Developers List
> Subject: Re: Opening up Maven CVS a bit...
>
>
> On Sunday 04 April 2004 14:01, Jason van Zyl wrote:
>
> > We are trying to do the exact opposite.
>
> Ok, fair enough.
>
> Q1; Do you have any pointers on how to publish plug-ins?
>
> Q2; But then you will require that the user download the 500
> plugins that you
> end up using, no?
>
>
> Cheers
> Niclas
> --
> +---------//-------------------+
> | http://www.bali.ac |
> | http://niclas.hedhman.org |
> +------//----------------------+
>
> ---------------------------------------------------------------------
> 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]
