RE: [vote] demote plugins
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 14, 2005 2:55 AM > To: Maven Developers List > Subject: Re: [vote] demote plugins > > Michal Maczka wrote: > > > > > I am using javacc in production in couple of project and it > actually > > works like charm for me (I am not using jjtree). Docs are definitly > > not up to date. I know that there is more people using it. So if I > > could cast no binding, user vote for that plugin it would be: -1. > > This is not about terminating plugins, but about improving > the out of the box usability. So while you might be using it > - that's fine, and you can continue to do so by downloading > the last release, or building from the sandbox. But until > someone steps up to maintain it and document it, I'd rather > not have it in the core distribution. Of all the plugins, it > and probably "release" are the ones that had a specific > complaint about its roadworthiness from a user. > I understand all that and from your perspective this is definitly a good thing. I don't know nothing about recent complaints reagrding javacc plugin. Really it just works for me. What I am saying is that from the user perspective it is reasonable to expect that builds which used to work out of the box with maven 1.0.X should also work with maven 1.1.x. (just minor version is changing). Believe it or not but there is a bunch of users who has never built maven plugin and even don't know how to manually download plugins. In case of the enterprises where nobody is controlling which version of maven they are using so if any of them will upgrade to maven 1.1 (or simply somebody new will just start directly using maven from version 1.1.0). For such people it is really a breaking and quite scary change. There is a general and a good rule often used while software platforms are evolving:: things go in, but they never go out (even if they are of dubious quality or better equivalents already exit). Java/Windows and other platforms try to follow that rule as full backward compatibility is a top priority for them. In your case m2 will hopefully come with high quality plugins, but removal of the plugin from the base distribution of m1 will actually downgrade user experience rather then improve it. People are (unfortunately) used to undocumented plugins but they are not used to disappearing ones. Note: I am not writing about plugins which are clearly broken or are not working at all. BTW: Are you going to publish all plugins from sandbox somewhere? regards Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
Brett Porter wrote: A single +1 indicates agreement to all of the below. Otherwise, please +1 - I don't use any of them neither and I believe/agree what you said. (my only exception would be Jira maybe - I used it a couple of months ago and it seemed to be working fine, so I'm +0 for this one) -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
On 6/14/05, Michal Maczka <[EMAIL PROTECTED]> wrote: > Brett Porter wrote: > > > javacc - experimental at best, no maintainer > > I am using javacc in production in couple of project and it actually > works like charm for me (I am not using jjtree). Docs are definitly not > up to date. I know that there is more people using it. So if I could > cast no binding, user vote for that plugin it would be: -1. > > Wouldn't it be nice to ask users - how many of them are using plugins > from your list? > I guess that there is probably bit more people following the traffic on > maven-user then on maven-dev list. > I am using JavaCC in production for two very important projects and it would be a problem if you remove it. So my -1 on this one. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
Michal Maczka wrote: I am using javacc in production in couple of project and it actually works like charm for me (I am not using jjtree). Docs are definitly not up to date. I know that there is more people using it. So if I could cast no binding, user vote for that plugin it would be: -1. This is not about terminating plugins, but about improving the out of the box usability. So while you might be using it - that's fine, and you can continue to do so by downloading the last release, or building from the sandbox. But until someone steps up to maintain it and document it, I'd rather not have it in the core distribution. Of all the plugins, it and probably "release" are the ones that had a specific complaint about its roadworthiness from a user. Wouldn't it be nice to ask users - how many of them are using plugins from your list? My original email said exactly that, and that's the step I'm taking now. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
+1 to all Vincent 2005/6/11, Brett Porter <[EMAIL PROTECTED]>: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with no > open bugs in JIRA will have their project deleted (we should work on a > server side solution to toss all the others into a sandbox bug project > and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is no > longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
Brett Porter wrote: Please vote on demoting the following plugins. They will be moved back to the sandbox, and will not be distributed with Maven 1.1. Any with no open bugs in JIRA will have their project deleted (we should work on a server side solution to toss all the others into a sandbox bug project and delete them too). Docs will be added to the backwards compat page explaining how you get the old releases, and what to do if you want to revive its development. An RFC will be sent to the user list first too. A single +1 indicates agreement to all of the below. Otherwise, please +1, -1 the individually. Any -1's will prevent that plugin from being demoted until we can resolve the issue. The vote is open until it is no longer Monday 13th in your part of the world. javacc - experimental at best, no maintainer I am using javacc in production in couple of project and it actually works like charm for me (I am not using jjtree). Docs are definitly not up to date. I know that there is more people using it. So if I could cast no binding, user vote for that plugin it would be: -1. Wouldn't it be nice to ask users - how many of them are using plugins from your list? I guess that there is probably bit more people following the traffic on maven-user then on maven-dev list. regards Michal -- Startuj z INTERIA.PL! >>> http://link.interia.pl/f186c - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] demote plugins
+1 Arnaud > > Please vote on demoting the following plugins. They will be > moved back to the sandbox, and will not be distributed with > Maven 1.1. Any with no open bugs in JIRA will have their > project deleted (we should work on a server side solution to > toss all the others into a sandbox bug project and delete them too). > > Docs will be added to the backwards compat page explaining > how you get the old releases, and what to do if you want to > revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. > Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open > until it is no longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works wizard - doesn't > work vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe javacc - > experimental at best, no maintainer jdee - no idea how to > test it, no maintainer jdeveloper - no maintainer junitdoclet > - no maintainer latex - not being maintained latka - not > being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to > artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be > culled in future if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
On Sat, 2005-06-11 at 17:37 +1000, Brett Porter wrote: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with no > open bugs in JIRA will have their project deleted (we should work on a > server side solution to toss all the others into a sandbox bug project > and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is no > longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained +1 > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
On Sat, 2005-06-11 at 17:37 +1000, Brett Porter wrote: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with no > open bugs in JIRA will have their project deleted (we should work on a > server side solution to toss all the others into a sandbox bug project > and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is no > longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained +1 > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] demote plugins
I as well use Simian and it works well. PMD's CPD report does the same, but they give different output (which is a different issue! :-) Not that I have a vote...+1 all too. I hope to see good info like "docbook - superseded by the SF one" included on the doc pages for the plugins, and why they are in the sandbox. E.g. I intend to use the docbook plugin soon, and I say "thanks for the tip" to use the SF one instead. :-) -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: Saturday, June 11, 2005 1:00 PM To: Maven Developers List Subject: Re: [vote] demote plugins +1 About jira and simian I'm using them to generate reports (although I don't look them usually) and they are working correctly. Regards Carlos Sanchez On 6/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with > no open bugs in JIRA will have their project deleted (we should work > on a server side solution to toss all the others into a sandbox bug > project and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is > no longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that tjdo - no > maintainer shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer webserver - out of date, no > maintainer aspectwerkz - no maintainer, out of date caller - never > used struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe javacc - experimental at > best, no maintainer jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer junitdoclet - no maintainer latex - not > being maintained latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact > plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in > future if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
+1 About jira and simian I'm using them to generate reports (although I don't look them usually) and they are working correctly. Regards Carlos Sanchez On 6/11/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with no > open bugs in JIRA will have their project deleted (we should work on a > server side solution to toss all the others into a sandbox bug project > and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is no > longer Monday 13th in your part of the world. > > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
On Sat, Jun 11, 2005 at 04:08:44PM +, Lukas Theussl wrote: > Brett Porter wrote: > > > >outstanding issues - bugs & feature requests: > >docbook - superseded by the SF one, I believe > >javacc - experimental at best, no maintainer > >jdee - no idea how to test it, no maintainer > >jdeveloper - no maintainer > >junitdoclet - no maintainer > >latex - not being maintained > >latka - not being maintained > > > > I don't know if I am entitled to vote but I find it a shame that the > latex plugin should be removed. Even though I have never used it myself, > I would certainly have done so if it would have worked properly. I am > quite sure that it would be useful for a number of people. > > I'd have to take some time and have a closer look at it, but in > principle I would be willing to take over its maintainance, if nobody > else does so. If you would like to take over this plugin I suggest you do so at the Maven Plugins project at Source Forge[1]. If you tell Brett your sf user id I'm sure Brett will add you to the project. [1]: http://maven-plugins.sourceforge.net/ -- Trygve signature.asc Description: Digital signature
Re: [vote] demote plugins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 This is a step in the right direction. These plugins can be revived if someone is willing to maintain them, and presently they drag down the perceived value of maven plugins as a whole. I know that in times past I've been reluctant to try new plugins based on the mess that some other plugins were (*cough* xdoclet *cough*). If this comes with a criteria for inclusion of plugin projects (or at least a confidence rating about the plugin's stability), I think we'll hit a point where people (like me) are confident that they will be able to actually use the plugins that are out there... - -john Brett Porter wrote: > > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCqxZiK3h2CZwO/4URArNXAJ9RHAa8P/SJKpIxIZR2FQnyBXG9eACggOT1 vS5yTG8xllwtIKfPkj9bkSA= =CtU2 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
Brett Porter wrote: outstanding issues - bugs & feature requests: docbook - superseded by the SF one, I believe javacc - experimental at best, no maintainer jdee - no idea how to test it, no maintainer jdeveloper - no maintainer junitdoclet - no maintainer latex - not being maintained latka - not being maintained I don't know if I am entitled to vote but I find it a shame that the latex plugin should be removed. Even though I have never used it myself, I would certainly have done so if it would have worked properly. I am quite sure that it would be useful for a number of people. I'd have to take some time and have a closer look at it, but in principle I would be willing to take over its maintainance, if nobody else does so. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SPAM: [vote] demote plugins
Brett Porter wrote: Please vote on demoting the following plugins. They will be moved back to the sandbox, and will not be distributed with Maven 1.1. Any with no open bugs in JIRA will have their project deleted (we should work on a server side solution to toss all the others into a sandbox bug project and delete them too). Docs will be added to the backwards compat page explaining how you get the old releases, and what to do if you want to revive its development. An RFC will be sent to the user list first too. A single +1 indicates agreement to all of the below. Otherwise, please +1, -1 the individually. Any -1's will prevent that plugin from being demoted until we can resolve the issue. The vote is open until it is no longer Monday 13th in your part of the world. +1 Emmanuel no outstanding issues: ashkelon - unmaintained, no idea if it works wizard - doesn't work vdoclet - only used by tasklist, will fold it into that tjdo - no maintainer shell - no maintainer outstanding issues, but nothing that requires being kept: appserver - out of date, no maintainer webserver - out of date, no maintainer aspectwerkz - no maintainer, out of date caller - never used struts - out of date, not being maintained outstanding issues - bugs & feature requests: docbook - superseded by the SF one, I believe javacc - experimental at best, no maintainer jdee - no idea how to test it, no maintainer jdeveloper - no maintainer junitdoclet - no maintainer latex - not being maintained latka - not being maintained Not to be removed now, but to get merged and removed by the final 1.1 release: - repository - not being maintained (move upload-bundle to artifact plugin) - release - moved used functionality to SCM plugin - j2ee - depended on by struts and ear, move the tag into ear Borderline (not included in this vote, but likely to be culled in future if they don't get fixed and nobody volunteers): - jbuilder (not of same level as other IDE plugins) - jcoverage (replaced by Corbetura) - jira - not working, no maintainer? - simian - not being maintained - jdiff - not being maintained Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] demote plugins
On Sat, Jun 11, 2005 at 05:37:48PM +1000, Brett Porter wrote: > Please vote on demoting the following plugins. They will be moved back > to the sandbox, and will not be distributed with Maven 1.1. Any with no > open bugs in JIRA will have their project deleted (we should work on a > server side solution to toss all the others into a sandbox bug project > and delete them too). > > Docs will be added to the backwards compat page explaining how you get > the old releases, and what to do if you want to revive its development. > An RFC will be sent to the user list first too. > > A single +1 indicates agreement to all of the below. Otherwise, please > +1, -1 the individually. Any -1's will prevent that plugin from being > demoted until we can resolve the issue. The vote is open until it is no > longer Monday 13th in your part of the world. +1 > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear > > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained > > Cheers, > Brett > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > signature.asc Description: Digital signature
RE: [vote] demote plugins
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: samedi 11 juin 2005 09:38 > To: Maven Developers List > Subject: [vote] demote plugins [snip] > no outstanding issues: > ashkelon - unmaintained, no idea if it works > wizard - doesn't work > vdoclet - only used by tasklist, will fold it into that > tjdo - no maintainer > shell - no maintainer > > outstanding issues, but nothing that requires being kept: > appserver - out of date, no maintainer > webserver - out of date, no maintainer > aspectwerkz - no maintainer, out of date > caller - never used > struts - out of date, not being maintained > > outstanding issues - bugs & feature requests: > docbook - superseded by the SF one, I believe > javacc - experimental at best, no maintainer > jdee - no idea how to test it, no maintainer > jdeveloper - no maintainer > junitdoclet - no maintainer > latex - not being maintained > latka - not being maintained > > Not to be removed now, but to get merged and removed by the final 1.1 > release: > - repository - not being maintained (move upload-bundle to artifact > plugin) > - release - moved used functionality to SCM plugin > - j2ee - depended on by struts and ear, move the tag into ear +1 to all above. > Borderline (not included in this vote, but likely to be culled in future > if they don't get fixed and nobody volunteers): > - jbuilder (not of same level as other IDE plugins) > - jcoverage (replaced by Corbetura) > - jira - not working, no maintainer? > - simian - not being maintained > - jdiff - not being maintained I'm using simian from time to time and jdiff is a plugin I'd love to use (I think I've used it once or twice but it wasn't flexible enough and I probably got to use jdiff directly from my maven.xml). Basically, I'd love that we be able to keep simian/jdiff. I also think the JIRA plugin should be kept and modified to generate a changes.xml file so that all other plugins manipulating changes.xml files can be used (announcement, xdocs, multichanges, etc). Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] demote plugins
Please vote on demoting the following plugins. They will be moved back to the sandbox, and will not be distributed with Maven 1.1. Any with no open bugs in JIRA will have their project deleted (we should work on a server side solution to toss all the others into a sandbox bug project and delete them too). Docs will be added to the backwards compat page explaining how you get the old releases, and what to do if you want to revive its development. An RFC will be sent to the user list first too. A single +1 indicates agreement to all of the below. Otherwise, please +1, -1 the individually. Any -1's will prevent that plugin from being demoted until we can resolve the issue. The vote is open until it is no longer Monday 13th in your part of the world. no outstanding issues: ashkelon - unmaintained, no idea if it works wizard - doesn't work vdoclet - only used by tasklist, will fold it into that tjdo - no maintainer shell - no maintainer outstanding issues, but nothing that requires being kept: appserver - out of date, no maintainer webserver - out of date, no maintainer aspectwerkz - no maintainer, out of date caller - never used struts - out of date, not being maintained outstanding issues - bugs & feature requests: docbook - superseded by the SF one, I believe javacc - experimental at best, no maintainer jdee - no idea how to test it, no maintainer jdeveloper - no maintainer junitdoclet - no maintainer latex - not being maintained latka - not being maintained Not to be removed now, but to get merged and removed by the final 1.1 release: - repository - not being maintained (move upload-bundle to artifact plugin) - release - moved used functionality to SCM plugin - j2ee - depended on by struts and ear, move the tag into ear Borderline (not included in this vote, but likely to be culled in future if they don't get fixed and nobody volunteers): - jbuilder (not of same level as other IDE plugins) - jcoverage (replaced by Corbetura) - jira - not working, no maintainer? - simian - not being maintained - jdiff - not being maintained Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
