You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2004/04/04 07:23:03 UTC
Opening up Maven CVS a bit...
Hi,
I would like the Maven community to discuss a solution where other Apache
projects are given a 'partitition' in Maven Plugins to create their own
solutions to be automatically included in Maven distros.
It wouldn't be harder than;
for PROJECT in `cat projectsfile` ; do
if [ -d /home/cvs/maven-plugins/$PROJECT ] ; then
echo "$PROJECT is already in maven-plugins. Resolve manually!"
else
mkdir /home/cvs/maven-plugins/$PROJECT
chmod g+w /home/cvs/maven-plugins/$PROJECT
chgrp $PROJECT /home/cvs/maven-plugins/$PROJECT
fi
done
Cheers
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Opening up Maven CVS a bit...
Posted by Corey Jewett <cj...@syntheticplayground.com>.
This works well, but it causes the currently released jar plugin to
create incorrect Manifests.
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJAR-22
Corey
On Sunday, Apr 4, 2004, at 01:12 US/Pacific, Eric Pugh wrote:
> 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:niclas@hedhman.org]
>> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Opening up Maven CVS a bit...
Posted by Eric Pugh <ep...@upstate.com>.
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:niclas@hedhman.org]
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Opening up Maven CVS a bit...
Posted by Niclas Hedhman <ni...@hedhman.org>.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Opening up Maven CVS a bit...
Posted by Jason van Zyl <jv...@maven.org>.
On Sun, 2004-04-04 at 00:23, Niclas Hedhman wrote:
> Hi,
>
> I would like the Maven community to discuss a solution where other Apache
> projects are given a 'partitition' in Maven Plugins to create their own
> solutions to be automatically included in Maven distros.
We are trying to do the exact opposite. We don't want them hosted under
Maven. If you have a plugin for project Foo, then develop the plugin in
Foo land. This is what Cactus does, this is what Torque does so there is
nothing stopping you from doing it too.
You can develop your plugins wherever you like and it's simple for users
to download them. We will ultimately keep what we consider to be core
but the rest of them will eventually be flushed out to places where
those interested in them can develop them.
We already have too many plugins that aren't properly taken care of.
> It wouldn't be harder than;
>
> for PROJECT in `cat projectsfile` ; do
> if [ -d /home/cvs/maven-plugins/$PROJECT ] ; then
> echo "$PROJECT is already in maven-plugins. Resolve manually!"
> else
> mkdir /home/cvs/maven-plugins/$PROJECT
> chmod g+w /home/cvs/maven-plugins/$PROJECT
> chgrp $PROJECT /home/cvs/maven-plugins/$PROJECT
> fi
> done
>
>
> Cheers
> Niclas
--
jvz.
Jason van Zyl
jason@maven.org
http://maven.apache.org
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org