I do extensive get development in Netbeans for GWT and very happy with the current setup minus increasing the maxmemory variable every time I restart Netbeans so I don't run out of memory when building the application. If I debug the project, I run in the GWT browser and can do incremental debug updates on code without restarting as long as method signatures don't change so I rarely have issues with startup time when debugging code. When I want to test in browser I simply run the project and it launches in my default browser fairly quickly. To do a clean build takes about 1 minute 20 seconds on a fairly fast box. Changing one file and selecting debug which will build and launch takes 1 minute 30 seconds where startup of gwt browser takes about 10 seconds. I would like to see faster incremental build times when changing only one file. I work around this by debugging/fixing bugs and doing incremental updates on the current debug session and test the new code. This way I don't repeat all the application steps to get to the same debug state to test the code changes. Netbeans does the update and recalls the method with the same values prior to the incremental update.
The main point is I have a very productive and working environment where I have a war file automatically built by netbeans and couldn't think of any way to make it easier and I do nothing to mess with the xml for building and deploying. No problems with you making changes but hopefully it doesn't break what already works well in netbeans. It would be nice if incremental builds was faster. Thanks Scooter Willis On Oct 15, 7:49 am, walden <[EMAIL PROTECTED]> wrote: > +1 well said. > > On Oct 14, 6:03 pm, Jason Essington <[EMAIL PROTECTED]> wrote: > > > Since creating a usable server side configuration in the embedded > > servlet container is all but impossible for anything but the simplest > > projects, I think that the choice of embedded server is a non-issue. > > > Since complicated configurations aren't really something you want to > > address in the embedded server, my vote would be for the simplest, > > fastest implementation that supports the simple case uses. > > > So, if Jetty starts faster and is lighter weight, then great, use it. > > > -jason > > > On Oct 13, 2008, at 4:48 PM, Bruce Johnson wrote: > > > > Hi everyone, > > > > Hope you're enjoying 1.5. > > > > The GWT team has started putting together a 1.6 roadmap, which we'll > > > publish as soon as we have it nailed down. Two of the areas we want > > > to work on for 1.6 are some improvements to hosted mode startup time > > > and a friendlier output directory structure (something that looks > > > more .war-like). > > > > As part of this effort, we've all but decided to switch the hosted > > > mode embedded HTTP server from Tomcat to Jetty. Would this break > > > you? (And if so, how mad would you be if we did it anyway?) We > > > figure most people who really care about the web.xml and so on are > > > already using "-noserver" to have full control over their server > > > config. > > > > Thanks, > > > Bruce- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
