I stand corrected on this plugin supporting 1.6. I haven't tried it, bur Mirko notes in another thread that it works as is, but doesn't use the new project structure and gives you a few warnings. To be more correct I should say we aren't going to support the new project structure for 1.6 with this project (at least that is my plan), and we don't yet know exactly what does and does not work, but it has been reported by others to work.
On Mar 30, 9:28 am, Charlie Collins <[email protected]> wrote: > This codehaus Mojo plugin merged the code from this plugin INTO ITSELF > some time back. This plugin has not merged any of the Mojo stuff > here. I think you may be reading directions/instructions at the > Codehaus location, and they are corrupt right now (they merged > everything, even the docs, last time I checked they had our docs > there). > > For documenation and examples and so on for THIS PROJECT > see:http://code.google.com/p/gwt-maven/. > > In the future there will not be new features added to this project (as > far as I know, other developers may have other plans, I don't plan to > do new work here). This project will be frozen once we have had a > chance to validate and clean up the codehaus GWT Maven plugin (the > developers there merged in our stuff, and I joined that project too, > but haven't yet had time to get familiar with it and call it set - I > still use this one in the meantime). > > The status of this plugin right now is *being maintained but no new > features added*. This plugin works great, and many people have used > it in production for years now (even though it says beta), but it does > not support GWT 1.6 (and I am hoping to NOT add GWT 1.6 support here, > that would be a new feature, which should happen over a Codehaus > Mojo). > > As for the schedule which many people may be curious about, I am done > with my other side project (book) that was talking up most of my non > day job time as of TODAY (woot!). That means I will start focusing on > getting this project polished for a final release (the current trunk > with all the patches, no new features though), and then, after that, I > will start working on the Mojo version to get familiar there and make > sure it is up to our standards, has all the same features, so on > (including documentation, archetype, etc). > > If you are a developer here, and you wish to start working on stuff > like 1.6 support now (Cooper, for example), please ping me so we can > discuss and I will get you added as a Mojo project member. > > On Mar 30, 8:14 am, ivo <[email protected]> wrote: > > > Hello fellow developers, > > > I'm a newbie to maven and to gwt-maven and I want to port my gwt > > project with this maven plugin. > > > I have been looking around the web and I'm finding it difficult to > > understand what's going on... What's the relation between gwt-maven > > and the codehaus plugin? I read that "GWT-maven plugin has merged with > > this plugin since version 1.1", does this mean that there is only > > plugin from now on? > > > I can't install the pluggin. What's the right maven command? > > mvn deploy:deploy-file -DgroupId=org.codehaus.mojo -DartifactId=gwt- > > maven-plugin -Dversion=1.1 -Dpackaging=jar -Dfile=??? -Durl=??? > > > Finally will I be able to use my gwt 1.6 project with the 1.1 version > > of the plugin? > > > Thanks in advance! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
