I was kind of thinking along the exact same lines as Arthur there. I don't want to be the only main guy on this thing, having more people involved would be beneficial for many reasons. Don't get me wrong, others have helped here too, it's not just me - but I have definitely been the *main* creator/developer/maintainer - others seem to come and go (which is understandable, this project is something like 2-3 years old, who knows why they heck I even do it ;)).
I think it would be in the best interest of everyone, in the long run, if the projects join and as many dedicated people as we can get are involved. Also, if this were a different type of project I might resist this a lot more. I really like the autonomy (and the tools) of a Google Code project, but the bottom line is this IS a *Maven* plugin, doing things more in the Maven standard path only makes sense (even if the Maven standard path is not necessarily something I am very familiar with, or entirely comfortable with). That said I also agree with Darren about the trust and the "frustration" that moving this project may cause. I hope, if and when it comes to it, that I can mitigate that by being very involved on the Apache/Codehaus side, and by not removing or just shutting down this project, but rather keeping it going until everyone is comfortable with the new project (until we all agree the new one runs fine, meets all the requirements, handles the use cases, etc). On Nov 25, 2:22 pm, "Arthur Kalmenson" <[EMAIL PROTECTED]> wrote: > I have to agree with jieryn, I think that unifying the plugin would be > in the best interest of the user base. It'll make sure that there is a > good official Maven plugin and one that has a larger team behind it. > As it stands, both plugins have their own useful features, so I'd like > to see them combined. > > Charlie, you and the team have done an excellent job and I love the > plugin, but you can definitely use more help. The more people there > are behind a project the better. > > -- > Arthur Kalmenson > > On Tue, Nov 25, 2008 at 9:24 AM, jieryn <[EMAIL PROTECTED]> wrote: > > > I think a unification would be in the best interests of the user base; > > there was already a lot of confusion as to which plugin should be used > > and configured, and the recent deployment of codehaus plugin to > > central did not help. > > > I reviewed the codehaus plugin about 6 months ago, and the 1.0.0 > > release doesn't seem to have improved things. The codehaus plugin > > seems to be significantly far behind the google plugin in: features, > > maturity, actual use/deployment. > > > I don't see any aspects to the codehaus plugin that would be > > beneficial to the google plugin. So, if a unification of the plugins > > would simply be the replacement of codehaus plugin in whole with the > > google plugin, then I wholeheartedly vote yes. I think it would be > > advantageous for the google plugin to fall under codehaus because, as > > you say, it is the path to true maven pluginhood. > > > Perhaps the codehaus plugin team could serve as a cleansing of the > > google plugin codebase, putting things into the formality expected of > > Maven plugins, etc. That would certainly be an advantage; especially, > > and I mean no offense Charlie (and team) as I am quite grateful to > > your hard work, there seems to be some peculiarities and uncertainties > > about how to do things the Maven way, at times. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
