I vote "yes" if the status, developer rights and community mood will not be disturbed by the merge and be fluently transformed to one project. Personally I like the way Charley leads this project and how everybody is willing to help to shift it to be better. Codehaus plugin has nice features (async interface generation, eclipse launchers) so by merging this two projects everybody will benefit. This gwt-maven plugin seems to be more mature and used but that is for further code examination.
>From license point of view if we state it is under ASF and then merge with Codehaus there shouldn't be a problem. Finally it will be good to see what will change by joining Codehaus from developer's view (the voice that matters ;) On 26. Nov, 04:13 h., [EMAIL PROTECTED] wrote: > IANAL BUUUUTTTT... Isn't this mitigated by Charlie, and the other > developers, owning the copyright to the code? They could simply change > the license at their whim. This is exactly how projects like MySQL can > offer dual licensed stuff, etc. > > On Tue, Nov 25, 2008 at 4:28 PM, Mirko Nasato <[EMAIL PROTECTED]> wrote: > > > But with this project being LGPL and the Codehaus one using the Apache > > license it's easy to foresee licensing issues in copying code > > directly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
