The normal process for deprecating a plugin is by calling a vote. Reasons are often: - moved to another team/project/etc. - overruled by another plugin - has become part of another plugin (or Maven itself) Some options for the site-documentation: - add a .htaccess file and redirect to the new site - add some bold deprecation-text on the index.html But this seems to be a special case. The site is kind of useless, but I think the plugin might be interesting. Maybe just delete the site, but leave the project in the sandbox. -Robert
Date: Mon, 16 May 2011 15:35:07 +0200 From: [email protected] To: [email protected] Subject: Re: [mojo-dev] http://mojo.codehaus.org/retroweaver-maven-plugin/ Your mail triggered me to think about this. Especially in this case where it looks like a dummy plugin with no use. Does anyone who's been here for a while know if there is such a process? Should we just vote and then (hopefully) go ahead? /Anders On Mon, May 16, 2011 at 15:30, Benson Margulies <[email protected]> wrote: Is there a process of deleting abandoned sandbox sites to reduce noise and confusion? On Mon, May 16, 2011 at 9:26 AM, Anders Hammar <[email protected]> wrote: > Seems to be a sandbox plugin. With all the quality and attention that > implies...:-) > > This specific plugin seems to be a default plugin stub that Jason created > ages ago. > > /Anders > > On Mon, May 16, 2011 at 15:05, Benson Margulies <[email protected]> > wrote: >> >> Is this alive or dead? Should that rather unhelpful maven site be there? >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
