>> Could someone with enough karma to enable write access handle this task? >> 1) Open up Maven 2.x Tomcat plugin project for writing >> 2) Move all tickets on the Mojo component "tomcat" to that project > AFAICS all issues are closed. > So what is the problem exactly ? > The most simple is IMHO to delete those issue with a bulk operation.
Well, I was thinking that no tickets should be removed as discussed in a separate mail thread. I supposed these ones were for a pre-release version, but I still think it's best to keep them if possible. I mean, why are we keeping retired components otherwise? /Anders > >> 3) Close the Maven 2.x Tomcat plugin again >> 4) Remove the "tomcat" component on the Mojo project >> >> I could do 2 and 4, if someone else does 1 and 3. But I guess one >> single person doing them all is faster. >> >> Thanks, >> /Anders >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > Olivier Lamy > Talend : http://talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > 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
