On Saturday, December 11, 2010 11:36:00 AM UTC, Thomas Broyer
wrote:Have you read the FAQ about the Google Plugin for Eclipse use
with Maven?
http://code.google.com/eclipse/docs/faq.html#gwt_with_maven



Some people are using "mvn jetty:run" instead of the suggested WTP
or "run 'mvn -Dgwt.compiler.skip=true package' whenever you change a
dependency".
We've been using the "mvn package" for a while before we chose to split
our shared, client, and server code in distinct Maven modules (which
would require a "mvn package" each time we change a shared or server
class, because most of our server code is itself a jar dependency of
the war module). We're now using WTP (with Jetty WTP) which speeds the
process, but some of my team mates have issues with it (some
dependencies, sometimes some classes, are not deployed correctly). I'm
evaluating using jetty:run but for now have some issues with workspace
dependency resolution in m2eclipse (I always had them but it wasn't
really an issue with "mvn package" as I could run it on the "root"
module, this is however not an option with jetty:run). That being said,
I'm new to maven (using it since early July this year; and WTP, using
it for a few weeks only), so it might be something I'm doing wrong.

Thomas,

Guess what? It's working now :)

I owe you some thanks for pushing me in the right direction. Prior to
your message I didn't even know what WTP was! That's why the FAQ didn't
make much sense to me. I just figured that DevMode's embedded server
would be handling it all. So, DevMode's server doesn't support
hot-deploying, and that's the whole point of using WTP I presume?

Anyway, now my setup is Jetty WTP. I can make changes to pom.xml and
then web.xml to bring Spring in - all without even restarting the
server. That's very cool! Eclipse can debug client-code and server-code
fine.

Thanks again,

Pete

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" 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/google-web-toolkit?hl=en.

Reply via email to