On Sunday, July 31, 2016 at 5:29:24 AM UTC+2, Paul Stockley wrote: > > I have a couple of different issues with the new RC1 build. On my mac > project, I get the following error when starting devmode from the initellij > debug launch config > > The code server is ready at http://127.0.0.1:9876/ > Code server started in 20.08 s ms > 2016-07-30 23:18:40.674:INFO:oejs.ServerConnector:main: Started > ServerConnector@62d60234{HTTP/1.1}{127.0.0.1:9876} > 2016-07-30 23:18:40.674:INFO:oejs.Server:main: Started @21690ms > 2016-07-30 23:18:40.834:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT > 2016-07-30 23:18:44.933:WARN:oejuc.AbstractLifeCycle:main: FAILED > c.g.g.d.s.j.WebAppContextWithReload@77a2f454{/,file:/Users/paul/Library/Caches/IntelliJIdea2016.2/gwt/react.cb437975/git-hub-work.1e824b8/run/www/,STARTING}{/Users/paul/Library/Caches/IntelliJIdea2016.2/gwt/react.cb437975/git-hub-work.1e824b8/run/www}: > > java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider > org.eclipse.jetty.apache.jsp.JuliLog not a subtype > java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider > org.eclipse.jetty.apache.jsp.JuliLog not a subtype >
I'd say you have apache-jsp libs in your WEB-INF/lib: https://github.com/gwtproject/gwt/issues/9343 On a much larger project on Windows, again using Intellj I get the > following error > > Connected to the target VM, address: '127.0.0.1:55385', transport: > 'socket' > Exception in thread "main" java.lang.IncompatibleClassChangeError: > Implementing class > […] > at java.lang.Class.forName(Class.java:348) at > com.google.gwt.dev.DevMode$ArgHandlerServer.setString(DevMode.java:179) > at > com.google.gwt.util.tools.ArgHandlerString.handle(ArgHandlerString.java:26) > at com.google.gwt.util.tools.ToolBase.processArgs(ToolBase.java:291) > at > com.google.gwt.dev.ArgProcessorBase.processArgs(ArgProcessorBase.java:30) > at com.google.gwt.dev.DevMode.main(DevMode.java:425) > That could be an incompatibility between libs. Given that this happens in ArgHandlerServer and with its default value (ToolBase#processArgs at line 291), I'd say maybe you have dependencies on other Jetty libs with versions different from the one used by GWT. AFAICT, Jetty really requires all its libs to be from the exact same version, as things could break even between minor (or even "patch") versions if you mix them. > Disconnected from the target VM, address: '127.0.0.1:55385', transport: > 'socket' > > I suspect it is something dumb on my part. It was working OK with a > significantly earlier snapshot build. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/76715bb0-7ce9-4e72-b95a-4e178c8b46f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
