Hmm, that sounded like there might be a hint in there somewhere. :-) > You could also create a launch configuration for the SuperDevMode code server directly because DevMode -noserver is the same as starting the main class CodeServer.
What does that mean in Eclipse, Jens? This is what I have for the DevMode "Program Arguments": -noserver -superDevMode -startupUrl http://localhost:8888/apps/default -war "${workspace_loc:/BBj/war}" -remoteUI "${gwt_remote_ui_server_port}:${unique_id}" -logLevel INFO -codeServerPort 9997 -bindAddress 0.0.0.0 com.basis.bbj.web.gwt.EnglishOnly On Monday, March 21, 2016 at 3:10:23 PM UTC-7, Jens wrote: > > With old/classic DevMode -noserver there is no jetty started at all so it > did not matter if you have a jetty-all-9.2.10.jar on classpath or not. > However with GWT 2.8 when executing DevMode -noserver the SuperDevMode > CodeServer will be started which uses its own embedded jetty > server/library. So now you have two jetty libraries on class path with > different versions and thats why you get the above error: a class file from > a wrong jetty version has been loaded. > > So yes, without that extra jetty library on your classpath would have just > worked ;-) > > You can fix your issue by removing any server side library from your > DevMode launch configuration. You could also create a launch configuration > for the SuperDevMode code server directly because DevMode -noserver is > the same as starting the main class CodeServer. The parameters used to > launch CodeServer are in your first post (Runing CodeServer with > parameters:....). > > -- J. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
