> -----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]
