I personally haven't yet had a chance to really even look at the Mojo one. I have agreed to work with Nicolas (the developer there) and merge things, as soon as I can, but I haven't had a chance yet. So that basically means I don't know what the status of the Mojo plugin is. I get the impression that this plugin (GWT-Maven) is doing more than that one (such as merge web xml, etc), but I don't know much about the Mojo one - yet.
My approach is going to be to keep this one going, and keep it supported, until such time as I can sign off on the Mojo one having all the same features as this one has. When that happens I will deprecate (but not remove or disable) this one. That said I would recommend the following: If you want a fairly stable plugin I can vouch for, then use this one. If you are willing to work with the changes that will be happening at Mojo as I start getting involved and merging things, and you want to help with the end goal - a unified plugin - then use that one. On Jan 7, 9:50 am, "P.G.Taboada" <[email protected]> wrote: > Hi Charlie, hi Arthur, > > thanks for your statements here. I am starting over a new project and > would like to know which one to use. I would like to use the -noserver > option sometimes. > > brgds, > > Papick > > On Dec 11 2008, 11:56 am, Charlie Collins <[email protected]> > wrote: > > > Exactly as Arthur stated. > > > I plan to deprecate this project ONLY AFTER I have had time to get in > > to the mojo project and help/verify/complete all that is there. The > > other mojo contributor is already working on migrating the code from > > this project over, but I have not had time to touch anything there yet > > (I don't know the status of the mojo plugin - haven't even had time to > > check out the code yet). I will try to get involved there as soon as I > > can, but it might a few weeks before I can jump in, and then when I do > > jump in I suspect it will take a few weeks to get it to where I am > > comfortable with it. > > > On Dec 10, 9:23 am, "Arthur Kalmenson" <[email protected]> wrote: > > > > No not yet. They're being merged and it's going to take some month(s) > > > for the codehaus one to be on-par. For now you can use the full name > > > to execute your goal correctly: > > > > mvn com.totsp.gwt:maven-googlewebtoolkit2-plugin:gwt > > > > -- > > > Arthur Kalmenson > > > > On Wed, Dec 10, 2008 at 8:16 AM, LEDUQUE Mickaël <[email protected]> > > > wrote: > > > > > Hello, > > > > > When I discovered that there was another plugin using the same prefix > > > > that gwt-maven, I filed a bug in their jira about the conflict > > > > (http://jira.codehaus.org/browse/MGWT-3). > > > > > Now, someone claims both plugins have been merged in the mojo project. > > > > We just need to be sure this is the case. > > > > > Is the mojo maven plugin now at the same level as the gwt-maven > > > > plugin? > > > > > Mickaël --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
