Steffen,

I think maintaining this in the same way as for cactus is a great idea.

+1.

Assuming similar votes come through, the last Apache based release will
still be included in RC2 but removed from future releases. We'll add the
appropriate "maven plugin:download" command to the release notes so that
people can find it (in the same way I intend to for RC2 and Cactus). We can
then cvs delete the code from the Apache CVS to avoid confusion.

Cheers,
Brett

> -----Original Message-----
> From: Steffen Pingel [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 23 March 2004 1:21 PM
> To: Maven Developers List
> Subject: maintainership of maven-statcvs-plugin
> 
> 
> Hi,
> 
> a new version of StatCvs-XML has been released. StatCvs-XML 
> is used as the 
> report engine in the maven-statcvs-plugin. The new release 
> contains lots of 
> bug fixes and a complete redesign of the report engine to support 
> customization. A detailed list of the changes is available at 
> http://statcvs-xml.berlios.de/changes-report.html.
> 
> We (the StatCvs-XML development team) have also updated the 
> maven-statcvs-plugin to support the new features of StatCvs-XML. 
> Documentation and a download link is available at 
> http://statcvs-xml.berlios.de/maven-plugin/.
> 
> As the development of StatCvs-XML and the plugin go hand in 
> hand, I would like 
> to suggest that the development of the maven plugin is moved to the 
> StatCvs-XML project. I am confident that we have aquired 
> enough jelly skill 
> to handle the (small) plugin codebase. 
> 
> I have already talked to Vincent Massol who has done a great job in 
> maintaining the plugin up to this point (he acctually suggested to 
> "externalize" the plugin and offered to upload the releases 
> to ibiblio).
> 
> What do you think?
> 
> Steffen
> 
> -- 
> Steffen Pingel - [EMAIL PROTECTED] - http://steffenpingel.de
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to