Hey Jason, The GWT issue tracker would be a fine place to report the feature request. I've added a new category to the tracker as well so we can properly categorize bugs filed against GWT-specific plugin features as they come in.
Cheers, -Sumit Chandel On Tue, Apr 14, 2009 at 8:00 AM, Jason Essington <[email protected]>wrote: > > I agree completely. > > If you've got a GWT project using a version of GWT where there is a > choice about which shell launcher to use (currently only 1.6.x) then > the user should be able to manually decide which one to use, or at > least override the plugin's decision. > > In my case, I've got a project that has been using -noserver since the > beginning of time (at least as far as GWT is concerned) and there is > no reason to fabricate the war/WEB-INF/web.xml file ... it is unneeded > and just noise in my project directory, but the plugin still requires > it if I want to use HostedMode ... I'd be a lot happier with a simple > checkbox in the launch configuration that says something like "Always > use HostedMode if available". > > I'm thinking this is probably something that would make a good feature > request ... in the GWT issue tracker I suppose? > > -jason > > On Apr 14, 2009, at 6:37 AM, Isaac Truett wrote: > > > It seems like, as long as the old GWTShell is going to be > > supported at all, there should be an option to explicitly switch > > between them. Or at least make the decision points more transparent, > > and reversible. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
