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