RE: [Maven-plugins-developer] Re: What is the right way of releasing a plugin?!

[Eric P. <ep...@up...>]

I'm not a big fan of #1...   That type of release made sense when
maven-plugins was brand new, and Maven didn't support downloading plugins
very well, or handle the rsync of plugins to Ibiblio.  But now, that just
doesnt' flow with how Maven works.

I would rather see the plugins released via #1 removed, and the page hidden,
and stick to #2, which should programmaticllya lead to #3.  I find using the
SF file release system slow and error prone, and doesn't add much.

I would also reather point folks at the various maven repo search websites
to use instead...

Eric

> -----Original Message-----
> From: mav...@li...
> [mailto:mav...@li...]On Behalf Of
> Jörg Schaible
> Sent: Friday, December 03, 2004 7:55 PM
> To: mav...@li...
> Subject: [Maven-plugins-developer] Re: What is the right way of
> releasing a plugin?!
>
>
> Andy Jefferson wrote:
>
> >> after a few complaints I'm puzzled about the proper way to release a
> >> plugin
> >>
> >> 1) releasing it on the SF main page
> >> 2) putting it under
> >> http://maven-plugins.sourceforge.net/repository/maven-plugins/plugins/
> >> 3) upload it to IBIBLIO such as the maven-javaapp-plugin
> >
> > IMO, 1) and 2) are what should be done.
>
>
> 2) can be done with plugin::remote-deploy (or so, can't remember, look at
> plugin-plugin's goals)
>
> - Jörg
>
> Sorry Andy for private mail, was intented for the list ... :(
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Maven-plugins-developer mailing list
> Mav...@li...
> https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer