Jose, I see that you're using the *mvn* commandline param. Why not use a built in Eclipse *run configuration*? While I have not used your exact configuration, I think you should be able to achieve it with something like the below using the maven-gwt-plugin<http://mojo.codehaus.org/gwt-maven-plugin/plugin-info.html> (or similar):
Goals: gwt:compile gwt:debug <https://lh3.googleusercontent.com/-ek5O5Dma2mw/T7fbVmnhucI/AAAAAAAABvw/S03dqUpZOUc/s1600/Selection_026.png> With a custom run configuration you should be able to get whatever custom launch steps you need at a single click from within Eclipse. You'll also need to add all the desired parameters (I've added startupUrl as an example). I don't have a list on me, but use the same parameters that the Eclipse *Web Application* starter uses under the *Arguments* tab. (pictured for my GWT-Maps-V3-Api project build). <https://lh6.googleusercontent.com/-0TpQrzrUBAg/T7fZoz7rFQI/AAAAAAAABvo/Z2OPG93hnaQ/s1600/Run+Configurations+_022.png> Still, I think you'll find it easier to use the *Web Application* launcher as it provides a nice UI for setting these parameters and generating the commandline string. My team uses the built-in server option of the Web Application configure and there is no need to startup Jetty in that case. I hope that helps. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/TR_F2ciOAmEJ. 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.
