On 1/24/06, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > Hello again, > > We have discussed this before somewhat superficially but never got to a > concrete conclusion so I'd like to call for a formal vote to finalize > this and collect some opinions if necessary. Let me point out and > emphasize that we are quite short of manpower for m1, so the main > motivation for this call is a lack of maintainers for a lot of plugins > (right now we still have 65 plugins that would ship with the core). > > The following are all plugins that I have never used myself, I have no > idea how and if they work and I don't want to invest time to find out. > They are all basically unmaintained, I therefore propose to move them > back into the sandbox: > > > Plugins to demote with work to do: > > [+1] repository - (do we need upload-bundle? I don't see where it's used)
Carlos, Brett, are you sure that we can always use these bundles with the m2 repo ? Do you continue to upload in the old m1 repository ? > [+1] release - move used classes to SCM plugin (Fabrizio?) > [+1] j2ee - move the resolver tag into ear and j2ee:validate-war to > war:validate (Stephane?) > > > Other unmaintained plugins: > > [] abbot [] castor - not working (see MPCASTOR-7) [] hibernate [] jbuilder - inferior to other IDE plugins [] jnlp [] uberjar - not working (see MPUBERJAR-8), inferior to javaapp-plugin +1 [] antlr [] cruisecontrol [] jcoverage - replaced by Cobertura [] jdiff [] nsis -1 I can maintain and release cruisecontrol and nsis. As noticed by Brett, nsis is used generate the maven installer for windows. I'll take a look at the others. [] jboss [] jetty +1, I'll help Vincent M to improve the cargo plugin. For the dependencies updates, it's not important because those plugins (even if they are not re-released) will use automatically the libraries defined in the maven 1.1-beta3 core. Arnaud A single +1 signifies agreement with demoting all of them, otherwise > please specify individually. I expect anybody who puts a -1 to any of > them to come up with an alternative solution (re-publish as is? take > over maintenance and get ready for m1.1? other?). > > Finally, I guess we will have to do a poll on the user list as well, > even though I don't know how binding that can be if we don't find a > maintainer. > > Here's my tentative +1, hope to hear from you within 72h. > > -Lukas > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
