Just another note on this thread, for debugging purposes the plugin also has a gwt:debug goal. Everything can be debugged via Eclipse, I am not saying I don't like that (I use Eclipse and I use the debugger). Starting the shell though, is done via the plugin, whether you want to debug it or not, and not from an Eclipse "launch configuration" - if that's what we are talking about by a "launch script."
If you want to launch the debug goal from Eclipse you can with m2eclipse. So in all I still think everything we are talking about here is already in the plugin, and it's abstracted away from a particular IDE which is a better approach (better than including anything specific to any particular IDE). On Nov 7, 12:53 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > Oh, I see now, sorry. This plugin (and the archetype) has nothing to > do with Eclipse though, intentionally. > > The m2Eclipse plugin might already be able to do that, I am not sure. > But I personally would not really want any IDE specific stuff mixed in > with this project. > > On Nov 7, 10:12 am, "David Durham, Jr." <[EMAIL PROTECTED]> > wrote: > > > On Thu, Nov 6, 2008 at 6:31 PM, Charlie Collins > > > <[EMAIL PROTECTED]> wrote: > > > > mvn gwt:gwt - launches the shell > > > mvn gwt:compile - runs the compiler (Though this goal is not intended > > > Absolutely. That's great. It could also generate a launch script, > > which is useful for debugging in eclipse. I'm just talking about the > > archetype, not the plugin per se. > > > -Dave --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
