Just point your output dir to your target dir with the codehouse plugin and simple ignore it... That what I do.... Works fine...
--Ed On Apr 16, 3:27 pm, Mark Renouf <mark.ren...@gmail.com> wrote: > The maven-gwt-plugin from codehaus is looking quite good at this > point. I recommend trying 1.1-SNAPSHOT. > > I just reported an issue with running unit tests (which has been fixed > in SVN, waiting on a new SNAPSHOT build). With that it does absolutely > everything I've expected (on all platforms, without local > configuration) and with very minimal setup (add the plugin, add a > dependency on gwt-user, done). > > The one remaining issue is the new build output format (WAR), and how > resources are deployed. I'm totally against having GWT compile > directly into /src/main/webapp. It's completely against the principles > of keeping your source tree clean and putting all artifacts under > target. If you stick with traditional maven approach, it means you > need to execute war:exploded first before launching hosted mode (and > again if you want to change something without restarting the hosted > mode). > > The other approach is stick with src/main/webapp and make sure the > clean plugin cleans out all GWT generated files. Again, this is really > not the right approach :-( > > On Apr 16, 8:48 am, Arthur Kalmenson <arthur.k...@gmail.com> wrote: > > > It would definitely be nice if the Google Eclipse plugin was build > > system agnostic, or at least gave you more configuration options. > > Maybe we should just file a issue with the Google Eclipse plugin (I > > can't find the Google Code project...)? > > > -- > > Arthur Kalmenson > > > On Thu, Apr 16, 2009 at 4:33 AM, Salvador Diaz <diaz.salva...@gmail.com> > > wrote: > > > >> * If you enable gwt support on your project, GWT SDK library is > > >> automatically added to the project, event if you already manage your > > >> dependencies with maven. You should be able to configure if you want > > >> the sdk to be included or not. > > >> * The plugin complains about output directory not set to "war/WEB-INF/ > > >> classes". We should be able to configure this in order to work in a > > >> standard maven way. > > > > Those are pretty good remarks, and worth of opening an issue in the > > > issue tracker. We could do it the other way round though, and let the > > > maven plugin configure everything to conform to GWT's expectations, > > > remember that Googlers are not really maven guys. > > > > Cheers, > > > > Salvador > > > > On Apr 16, 10:09 am, johann_fr <johann.vanack...@gmail.com> wrote: > > >> I totally agree on the fact that gwt team should not provide the maven > > >> plugin, the codehaus one can do the job. They should just take care of > > >> beeing able to integrate with any build system. > > > >> My problems with the current google eclipse plugin : > > > >> Johann > > > >> On 16 avr, 08:50, Murray Waters <murray.wat...@gmail.com> wrote: > > > >> > It is in the snapshots repository. > > > >> >http://snapshots.repository.codehaus.org/org/codehaus/mojo/gwt-maven-... > > > >> > You will need to add the repository > > >> > ashttp://snapshots.repository.codehaus.org/ > > >> > I believe. > > > >> > On Apr 16, 12:33 pm, Keith Willard <keith.will...@gmail.com> wrote: > > > >> > > Where is the snapshot respository where the versions 1.1-SNAPSHOT > > >> > > codehaus gwt-maven-plugin lives? only the 1.0 is in the central > > >> > > repository. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
