[Maven-plugins-developer] Re: Supporting Maven2 - WAS Re: How to contribute to the Weblogic plugin

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

Hi Scott,

+) sf.net maven plugins is a breeding ground for plugins - a lot of 
committers and no pressure. If a plugin becomes popular enough to be 
moved to codehaus or core maven plugins that's fine - mission completed

+) this is not the first and will not the last plugin moving out - the 
PMD plugin moved over to Maven a long time ago

Cheers,

Siegfried Goeschl


Scott Ryan wrote:
>>From the looks of it many of the existing sf.net maven plugins are moving
> over to codehaus mojo project.  It is an unusual process to get it accepted
> over there but I may go ahead and submit it over there since they already
> have a pretty thorough setup to automatically build and maintain the plugins
> as part of the Maven 2 process.  They have jira support for each plugin as
> well.
> 
> I am open to any input that anyone has for me not to move the Weblogic Maven
> 2 plugin but I just want to get it delivered out to the community for
> feedback and further enhancement.  I am sensitive to the fact this plugin
> had it genesis at SourceForge and that I am just a late entrant to the
> development cycle.   I want to keep the plugin alive and growing and
> anyplace that we can put it to  get the community involved is a good thing.
> 
> If we can come up with a structure or plan among the maven development
> community within sourceforge I am more than happy to support  that as well
> but the community looks a little stronger at codehaus.
> 
> I welcome your input and support.
> 
> Scott Ryan
> Chief Technology Officer
> Soaring Eagle L.L.C.
> sc...@th...
> www.soaringeagleco.com
> (303) 263-3044
> 
> -----Original Message-----
> From: Siegfried Goeschl [mailto:sie...@it...]
> Sent: Thursday, December 01, 2005 4:06 AM
> To: Scott Ryan; mav...@li...
> Subject: Supporting Maven2 - WAS Re: How to contribute to the Weblogic
> plugin
> 
> 
> Hi Scott,
> 
> I was the original author but I'm not the owner of the plugin - it
> became your kid a long time ago ... :-). Consequently is the decision
> where to host the plugin yours.
> 
> Since I'm out of touch with Maven 2 plugin development - what are the
> current plans for supporting the development of Maven 2 plugins?
> 
> If there are no further plans/ideas I propose
> 
> +) creating ${CVSROOT}/maven-plugins/maven2-plugins/ in parallel to the
> existing ${CVSROOT}/maven-plugins/maven-plugins/ directory
> 
> +) setting up a master build fro the Maven 2 plugins
> 
> +) updating the website to distict between Maven 1 and Maven 2
> 
> Cheers,
> 
> Siegfried Goeschl
> 
> 
> Scott Ryan wrote:
> 
>>Hi,
>>I wanted to follow up on the version 2 of the plugin.  I have been
>>swamped with requests for the plugin but it is a pain to build and
>>distribute on an individual basis so I wanted to put the code up on the
>>Sourceforge repository but not sure if there was decision to start a new
>>Maven 2 tree.   Another alternative would be to put it over at codehaus
>>or on apache proper.  Not sure I would get permission to put it on
>>Apache but codehaus has expressed interest in hosting it to combine it
>>with the Cargo plugin.
>>
>>Since you are the owner and orginal author of the plugin what do you
>>think should be done?  I really want to put the version 2.0 plugin out
>>to the public and get feedback via Jira asap.  I also want to see about
>>automating the build process so I can continue to upgrade the plugin as
>>I have time.
>>
>>I look forward to your input.
>>
>>
>>Scott Ryan
>>Chief Technology Officer
>>Soaring Eagle L.L.C.
>>sc...@th...
>>www.soaringeagleco.com
>>(303) 263-3044
>>
>>
> 
> 
> 
>