I can't answer that, I don't use noserver. I know some folks here have made a lot of progress with noserver and getting changes to show up automatically - but back in the day that was one of the reasons I didn't use noserver (the rpc files having to be redeployed, AND the fact that noserver doesn't support GWTTestCase based tests). (That's also one of the reasons we went so far with GWT-Maven to make it easy to manipulate the embedded server - so that the embedded server can support other non GWT servlets, JDNI, DataSources, filters, security, etc, etc, etc - all without any manual work.)
Maybe others here can help more with noserver though, I know a lot of people use it - anyone? On Dec 9, 12:29 pm, "P.G.Taboada" <[EMAIL PROTECTED]> wrote: > Hi, > > I did setup the -noserver thingy succesfully and I am happy with > jetty. The only thingy that's missing is a way of automatically adding > the required files to the running jetty (I mean the startup js, the > host hmtl, the static ressources and the rpc files). The "static" > files are easy to setup, but what about the rpc files? Everytime I > touch something I need to regenerate/ redeploy this files. > > How are you guys handling this? > > brgds, > > Papick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
