maven-plugins-developer

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

[Siegfried G. <sie...@it...>]

Hi folks,

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

IMHO 1) is a must-have since people look at the plugins and think 
"hey-this is really ancient"

Cheers,

Siegfried Goeschl

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

[Andy J. <an...@aj...>]

> 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.

3) is supposed to be automatic with the changes Brett made a couple of months 
ago

-- 
Andy

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

[Brett P. <bre...@gm...>]

correct.

you can follow this:
http://maven.apache.org/reference/developers/releasing-plugins.html

apart from the Apache specific stuff.

Cheers,
Brett


On Fri, 3 Dec 2004 17:26:12 +0000, Andy Jefferson <an...@aj...> 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.
> 
> 3) is supposed to be automatic with the changes Brett made a couple of months
> ago
> 
> --
> Andy
> 
> 
> 
> 
> -------------------------------------------------------
> 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
>

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

[S. <joe...@gm...>]

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 ... :(

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

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

[Brett P. <bre...@gm...>]

On Sun, 5 Dec 2004 10:11:16 +0100, Eric Pugh <ep...@up...> wrote:
> 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.

Not so much an issue of not being how Maven works. We could probably
automate making an SF release in some way if that was desired. But I
think it doesn't add the benefit, as you mention later.

> 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.

If it isn't being updated, probably best to remove them all. If you
can somehow add a link that would send them to the downloads page -
even better.

Cheers,
Brett