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