Re: GWT 2.8 RC1 - Could not merge 2 super sourced packages
I compared emulated classes in 'java.util' and 'java.beans' packages of GWT and GWTx and I found *java.util.Locale.java* which emulated in both packages. By removing java.util.Locale.java from emulated classes of GWTx, problem solved. Thanks Thomas. On Tue, Aug 2, 2016 at 9:44 AM, Ali Jalal wrote: > Hi, > > I compiled project with -strict and almost same errors logged (I think GWT > compiler does not merge 2 super-source packages like 'java.util' and > 'java.beans'). Here is the stacktrace: > > [java] Compiling module com.test.sample.Sample > [java]Tracing compile failure path for type > 'com.google.gwt.cell.client.EditTextCell' > [java] [ERROR] Errors in > 'com/google/gwt/cell/client/EditTextCell.java' > [java] [ERROR] Line 336: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.dom.builder.client.DomStylesBuilder' > [java] [ERROR] Errors in > 'com/google/gwt/dom/builder/client/DomStylesBuilder.java' > [java] [ERROR] Line 113: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.dom.client.DataTransfer' > [java] [ERROR] Errors in > 'com/google/gwt/dom/client/DataTransfer.java' > [java] [ERROR] Line 127: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.cellview.client.AbstractCellTable' > [java] [ERROR] Errors in > 'com/google/gwt/user/cellview/client/AbstractCellTable.java' > [java] [ERROR] Line 744: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 477: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.client.ui.MultiWordSuggestOracle' > [java] [ERROR] Errors in > 'com/google/gwt/user/client/ui/MultiWordSuggestOracle.java' > [java] [ERROR] Line 534: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.dom.client.HeadingElement' > [java] [ERROR] Errors in > 'com/google/gwt/dom/client/HeadingElement.java' > [java] [ERROR] Line 91: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.client.ui.AbsolutePanel' > [java] [ERROR] Errors in > 'com/google/gwt/user/client/ui/AbsolutePanel.java' > [java] [ERROR] Line 280: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.client.ui.UIObject' > [java] [ERROR] Errors in > 'com/google/gwt/user/client/ui/UIObject.java' > [java] [ERROR] Line 657: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 775: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.safehtml.shared.UriUtils' > [java] [ERROR] Errors in > 'com/google/gwt/safehtml/shared/UriUtils.java' > [java] [ERROR] Line 240: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 235: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 84: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.cellview.client.CellBasedWidgetImplTrident' > [java] [ERROR] Errors in > 'com/google/gwt/user/cellview/client/CellBasedWidgetImplTrident.java' > [java] [ERROR] Line 253: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 191: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 157: ROOT cannot be resolved or is not a > field > [java] [ERROR] Line 245: ROOT cannot be resolved or is not a > field > [java] [ERROR] Errors in > 'com/google/gwt/user/cellview/client/CellBasedWidgetImpl.java' > [java] [ERROR] Line 74: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.user.cellview.client.CellBasedWidgetImpl' > [java] [ERROR] Errors in > 'com/google/gwt/user/cellview/client/CellBasedWidgetImpl.java' > [java] [ERROR] Line 74: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.dom.builder.shared.HtmlStylesBuilder' > [java] [ERROR] Errors in > 'com/google/gwt/dom/builder/shared/HtmlStylesBuilder.java' > [java] [ERROR] Line 111: ROOT cannot be resolved or is not a > field > [java]Tracing compile failure path for type > 'com.google.gwt.view.client.DefaultSelectionEventManager' > [java] [ERROR] Errors in > 'com/google/gwt/view/client/DefaultSelectionEventManager.java' > [j
Re: Cascading GWT Application ?
Hey there.
I come back there to give you my final approach of this problem.
I create a Main Module who inherits of all my needed modules and specify my
onlyone entry-point. It looks like that :
Java side I manage my applications (modules) states and their history. It's
a kind of router for all my webapp.
For that in my onModuleLoad I initialise my History.addValueChangeHandler
function with all known states of my modules, then, and I charge them in a
declared "divMain" div in my html with a public function like that :
public void chargeMainModule(String appName, String state) {
RootPanel.get("divMain").clear();
App1 app1;
App2 app2;
switch (appName) {
case "Init":
app1 = new App1();
app1.onModuleLoadByMain("divMain");
app2 = new App2();
app2.onModuleLoadByMain("divMain");
break;
case "App1":
app1 = new App1();
app1.onModuleLoadByMain("divMain");// The string argument is the div's
name to charge the module.
addInUrl("mod", "App1", 0); // addInUrl is the main's function to manage a
key and a value in the url at the specified lvl.
break;
case "App2":
app2 = new App2();
app2.onModuleLoadByMain("divMain");
addInUrl("mod", "App2", 0);
break;
default:
break;
}
}
Then, I create my other modules with their own inherits and without
entry-point ! It's my main's chargeModule function who will trigger the
code in my module.
- I externalise as well the RPC Call. So all my module got a pointer on my
RPC project, and this one is collecting all the RPC client / server and
shared code. It's usefull for deployment, enjoyable for developping to not
recreate things already done etc... My servlet is put in my web.xml of my
main by application route. Ex : /main/app1/greeting and this is pointed to
my Implement class in my RPC project
- Common code, like connectLdap for example should so be placed in an other
project (gwt module) called ExternalTools. This allow to use global class
or function everywhere in my workspace.
- I create to finish a skeleton project who emulate my ldap login, using
the RPC project and charge one module at once... so I can dev my module
without using my main, but using the skeleton project, totally
independently. Really useful for external development.
So my current project seems like :
Main
|-- instanciate --> Menu (who get instance of main to launch
chargeModule function with app and div argument)
|-- instanciate --> App1 --- using --> RPC
|-- instanciate --> App2 --- using --> RPC
| |
| using if necessary
| |
| V
|-- instanciate --> ExternalTools
Skeleton (Using for dev)
|-- instanciate --> App1 -- using --> RPC
| |
| using if necessary
| |
| V
|-- instanciate --> ExternalTools
For deployment, I have so only one .war, the only thing I have to do before
uploading it on tomcat is to copy paste the class of my RPC project in my
classes folder of my main's war. A easy bash is doing well the job.
So at the moment, all is working perfectly, my module loading and
navigation is pretty fluid and clean and well separate.
I given up on maven, who is complicating (in my opinion) all the works
done. I gave a try to rest, but I found RPC easy enough at the moment for
us, and it responsed well at our need !
If you have questions, observations or advices, I will be glad to read :)
PS : Sorry for my english, I wrote this post quickly and some terrible
mistakes have should appears ! :D
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: 2.8.0 RC1 is here!
Got my application compiled and running, just needed to update a few dependencies. Since I am using a report generator, I have the JDT compiler on my classpath, solved it by adding the exact same version that got bundled in gwt-dev into my app. Interestingly I am having troubles with server refresh (not restart) in intellij: java.util.concurrent.RejectedExecutionException: org.eclipse.jetty.annotations.AnnotationConfiguration$1@2a5ec0a4 at org.eclipse.jetty.util.thread.QueuedThreadPool.execute(QueuedThreadPool.java:362) at org.eclipse.jetty.annotations.AnnotationConfiguration.scanForAnnotations(AnnotationConfiguration.java:541) at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:447) at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:479) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1337) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505) any tips/ tricks? -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
Hi, I tried GWT 2.8.0 RC1 and get this error. Any ideas? Compiling... [ERROR] An internal compiler exception occurred com.google.gwt.dev.jjs.InternalCompilerException: Error constructing Java AST at com.google.gwt.dev.jjs.impl.GwtAstBuilder.translateException(GwtAstBuilder.java:3886) at com.google.gwt.dev.jjs.impl.GwtAstBuilder.getInternalCompilerException(GwtAstBuilder.java:4291) at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(GwtAstBuilder.java:3985) at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(GwtAstBuilder.java:3825) at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(GwtAstBuilder.java:3860) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:129) at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470) at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:1089) at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:325) at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:548) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:479) at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:465) at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423) at com.google.gwt.dev.Precompile.precompile(Precompile.java:222) at com.google.gwt.dev.Precompile.precompile(Precompile.java:202) at com.google.gwt.dev.Precompile.precompile(Precompile.java:143) at com.google.gwt.dev.Compiler.compile(Compiler.java:204) at com.google.gwt.dev.Compiler.compile(Compiler.java:155) at com.google.gwt.dev.Compiler.compile(Compiler.java:144) at com.google.gwt.dev.Compiler$1.run(Compiler.java:118) at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) at com.google.gwt.dev.Compiler.main(Compiler.java:125) Caused by: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.lookup.MethodBinding.isDefaultMethod()Z at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMethod(GwtAstBuilder.java:4080) at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(GwtAstBuilder.java:3975) ... 21 more [ERROR] at DateTimeFormatInfoImpl_es_CL.java(22): public class DateTimeFormatInfoImpl_es_CL extends DateTimeFormatInfoImpl_es_419 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
*Caused by: java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.lookup.MethodBinding.isDefaultMethod()Z* Check your dependencies. Looks like you have an old JDT on class path and GWT requires a newer one. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT Material - Video tutorial #1
> > please suggestion > GWT Build Project Remove # Token .. ex : http://abc.com/#kkk replace http://abc.com/kkk > > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
gwt developer plugin can't be installed
i can't install gwt developer plugin for chrome now,when i click the button,it says it's lost or be deleted? how can i debug gwt now? anyone helps me? -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
js is broken after I add components to top level GWT class
I've added a new display panel type component to a GWT app and now there is a error on the js console as below. The Java compiles fine and gwtc compiles without error. What can be wrong? regards, John [java] Aug 02, 2016 3:32:42 PM java.util.prefs.WindowsPreferences [java] WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x8002. Windows RegCreateKeyEx(...) returned error code 5. [java] Compiling module chat.app [java]Compiling 5 permutations [java] Compiling permutation 0... [java] Compiling permutation 1... [java] Compiling permutation 2... [java] Compiling permutation 3... [java] Compiling permutation 4... [java]Compile of permutations succeeded [java]Compilation succeeded -- 31.637s [java] Linking into C:\Users\John\workspace\Chat_GWT1\war\app; Writing extras to C:\Users\John\workspace\Chat_GWT1\extras\app [java]Link succeeded [java]Linking succeeded -- 2.162s Uncaught TypeError: Cannot read property 'J' of undefined 1. ed @ app-0.js:762 vd @ app-0.js:505 jw @ app-0.js:268 fc @ app-0.js:861 Z @ app-0.js:874 _s @ app-0.js:479 g @ app-0.js:769 Jg @ app-0.js:384 Mg @ app-0.js:540 (anonymous function) @ app-0.js:541 Xs @ app-0.js:770 (anonymous function) @ app-0.js:879 (anonymous function) @ VM724:1 m @ app.nocache.js:9 (anonymous function) @ app.nocache.js:10 d @ app.nocache.js:6 (anonymous function) @ app.nocache.js:7 -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
redirect GWT application URL With out # sign..
http://abcc.com/#master replace http://abcc.com/master -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: js is broken after I add components to top level GWT class
The code tries to call a function / read a property of an undefined value. So in Java terms its a classic NullPointerException, so your code most likely has a bug. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: gwt developer plugin can't be installed
Either downgrade your browser to an older version which still supports the GWT browser plugin or use GWT SuperDevMode which does not require a browser plugin at all. You can search this group, there are a lot of threads about that topic. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
Thanks for the hint. Yes, the problem was that GWT SDK duplicates these JDT classes instead of depending on the corresponding library. Then gradle could not resolve this version conflict and kept the old JDT. Forcing a higher version fixed it. On Tuesday, August 2, 2016 at 4:35:37 PM UTC+2, Jens wrote: > > *Caused by: java.lang.NoSuchMethodError: > org.eclipse.jdt.internal.compiler.lookup.MethodBinding.isDefaultMethod()Z* > > > Check your dependencies. Looks like you have an old JDT on class path and > GWT requires a newer one. > > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
On Tuesday, August 2, 2016 at 5:50:22 PM UTC+2, Uwe Maurer wrote: > > Thanks for the hint. Yes, the problem was that GWT SDK duplicates these > JDT classes instead of depending on the corresponding library. > JDT is the only dependency that's still bundled into GWT, and this is the case because a) it uses a patched JDT (for a memory issue) and b) it uses internal APIs that are "normally" hidden into a JAR (yes, a JAR inside a JAR) and aren't available in any artifact in any Maven repo (that I know of). Note: GWT has always bundled its dependencies. It's only starting with 2.8.0-rc1 that dependencies are "referenced" instead; except for JDT. BTW, what's the reason you have JDT and gwt-dev in the same classpath/scope/configuration? Are you using JDT in client-side code? (a GWT generator?) If not, Gradle is flexible enough so you can correctly segregate dependencies depending on their use. -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
Great that most dependencies are referenced now. You are right, the extra JDT library should not even be on the GWT classpath. We use the gwt-gradle-plugin to compile GWT projects with gradle, maybe our configuration is not correct there. On Tuesday, August 2, 2016 at 6:03:37 PM UTC+2, Thomas Broyer wrote: > > > > On Tuesday, August 2, 2016 at 5:50:22 PM UTC+2, Uwe Maurer wrote: >> >> Thanks for the hint. Yes, the problem was that GWT SDK duplicates these >> JDT classes instead of depending on the corresponding library. >> > > JDT is the only dependency that's still bundled into GWT, and this is the > case because a) it uses a patched JDT (for a memory issue) and b) it uses > internal APIs that are "normally" hidden into a JAR (yes, a JAR inside a > JAR) and aren't available in any artifact in any Maven repo (that I know > of). > > Note: GWT has always bundled its dependencies. It's only starting with > 2.8.0-rc1 that dependencies are "referenced" instead; except for JDT. > > BTW, what's the reason you have JDT and gwt-dev in the same > classpath/scope/configuration? Are you using JDT in client-side code? (a > GWT generator?) If not, Gradle is flexible enough so you can correctly > segregate dependencies depending on their use. > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Dev mode issue after updating to rc1
Hi, I tried updating my project here: https://github.com/gwidgets/gwty-leaflet-starter-guide from 2.8.0-beta1 to 2.8.0-rc1, but I got the below issue while trying to run dev mode or deploy to a server. It works fine with beta1. java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider org.eclipse.jetty.apache.jsp.JuliLog not a subtype [ERROR] at java.util.ServiceLoader.fail(ServiceLoader.java:239) [ERROR] at java.util.ServiceLoader.access$300(ServiceLoader.java:185) [ERROR] at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) [ERROR] at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) [ERROR] at java.util.ServiceLoader$1.next(ServiceLoader.java:480) [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:78) [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:66) [ERROR] at org.apache.jasper.servlet.JspServlet.(JspServlet.java:69) [ERROR] at org.eclipse.jetty.jsp.JettyJspServlet.(JettyJspServlet.java:39) [ERROR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [ERROR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [ERROR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [ERROR] at java.lang.reflect.Constructor.newInstance(Constructor.java:423) [ERROR] at java.lang.Class.newInstance(Class.java:442) [ERROR] at org.eclipse.jetty.server.handler.ContextHandler$Context.createInstance(ContextHandler.java:2372) [ERROR] at org.eclipse.jetty.servlet.ServletContextHandler$Context.createServlet(ServletContextHandler.java:1166) [ERROR] at org.eclipse.jetty.servlet.ServletHolder.newInstance(ServletHolder.java:1207) [ERROR] at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:588) [ERROR] at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396) [ERROR] at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871) [ERROR] at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298) [ERROR] at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349) [ERROR] at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342) [ERROR] at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741) [ERROR] at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505) [ERROR] at com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:552) [ERROR] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [ERROR] at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) [ERROR] at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114) [ERROR] at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) [ERROR] at org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:140) [ERROR] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [ERROR] at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132) [ERROR] at org.eclipse.jetty.server.Server.start(Server.java:387) [ERROR] at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114) [ERROR] at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61) [ERROR] at org.eclipse.jetty.server.Server.doStart(Server.java:354) [ERROR] at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) [ERROR] at com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:761) [ERROR] at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:630) [ERROR] at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:923) [ERROR] at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:706) [ERROR] at com.google.gwt.dev.DevMode.main(DevMode.java:426) [ERROR] 2016-08-02 21:47:03.384:WARN:oejuc.AbstractLifeCycle:main: FAILED org.eclipse.jetty.server.handler.RequestLogHandler@17192bc: java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider org.eclipse.jetty.apache.jsp.JuliLog not a subtype [ERROR] java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider org.eclipse.jetty.apache.jsp.JuliLog not a subtype [ERROR] at java.util.ServiceLoader.fail(ServiceLoader.java:239) [ERROR] at java.util.ServiceLoader.access$300(ServiceLoader.java:185) [ERROR] at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) [ERROR] at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) [ERROR] at java.util.ServiceLoader$1.next(ServiceLoader.java:480) [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:78) [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:66) [ERROR] at org.apache.jasper.servlet.JspServlet.(Jsp
Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST
On Tuesday, August 2, 2016 at 6:35:05 PM UTC+2, Uwe Maurer wrote:
>
> Great that most dependencies are referenced now.
>
> You are right, the extra JDT library should not even be on the GWT
> classpath.
> We use the gwt-gradle-plugin to compile GWT projects with gradle, maybe
> our configuration is not correct there.
>
I don't know gwt-gradle-plugin well, but quickly looking at its source, I
don't think you can do that (without splitting the 'war' and 'gwt' into
separate subprojects)
Maybe if you use something like:
configurations.gwt.exclude group: 'xxx.xxx.xxx', module: 'jdt'
or possibly using module replacement to tell Gradle that JDT is "replaced"
by gwt-dev whenever both are in the same configuration:
dependencies {
modules {
module("xxx.xxx.xxx:jdt") {
replacedBy("com.google.gwt:gwt-dev")
}
}
}
But because gwt-gradle-plugin doesn't use Configuration#extendsFrom, I'm
not sure it'll work.
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Re: Dev mode issue after updating to rc1
Works for me. Could it be that you forgot to override gwt-maven-plugin's
dependencies?
https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html
Also works well with "mvn appengine:devserver_start && mvn
gwt:run-codeserver" (and "mvn appengine:devserver_stop" when finished)
after I added:
${project.build.directory}/${project.build.finalName}
to the gwt-maven-plugin configuration.
On Tuesday, August 2, 2016 at 9:56:46 PM UTC+2, zakaria amine wrote:
>
> Hi,
>
>
> I tried updating my project here:
> https://github.com/gwidgets/gwty-leaflet-starter-guide from 2.8.0-beta1
> to 2.8.0-rc1, but I got the below issue while trying to run dev mode or
> deploy to a server. It works fine with beta1.
>
> java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider
> org.eclipse.jetty.apache.jsp.JuliLog not a subtype
> [ERROR] at java.util.ServiceLoader.fail(ServiceLoader.java:239)
> [ERROR] at java.util.ServiceLoader.access$300(ServiceLoader.java:185)
> [ERROR] at
> java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376)
> [ERROR] at
> java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
> [ERROR] at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
> [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:78)
> [ERROR] at org.apache.juli.logging.LogFactory.(LogFactory.java:66)
> [ERROR] at org.apache.jasper.servlet.JspServlet.(JspServlet.java:69)
> [ERROR] at
> org.eclipse.jetty.jsp.JettyJspServlet.(JettyJspServlet.java:39)
> [ERROR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [ERROR] at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [ERROR] at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> [ERROR] at java.lang.Class.newInstance(Class.java:442)
> [ERROR] at
> org.eclipse.jetty.server.handler.ContextHandler$Context.createInstance(ContextHandler.java:2372)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletContextHandler$Context.createServlet(ServletContextHandler.java:1166)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletHolder.newInstance(ServletHolder.java:1207)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:588)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:396)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:871)
> [ERROR] at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
> [ERROR] at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> [ERROR] at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> [ERROR] at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> [ERROR] at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> [ERROR] at
> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:552)
> [ERROR] at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> [ERROR] at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> [ERROR] at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> [ERROR] at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> [ERROR] at
> org.eclipse.jetty.server.handler.RequestLogHandler.doStart(RequestLogHandler.java:140)
> [ERROR] at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> [ERROR] at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> [ERROR] at org.eclipse.jetty.server.Server.start(Server.java:387)
> [ERROR] at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> [ERROR] at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> [ERROR] at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> [ERROR] at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> [ERROR] at
> com.google.gwt.dev.shell.jetty.JettyLauncher.start(JettyLauncher.java:761)
> [ERROR] at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:630)
> [ERROR] at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:923)
> [ERROR] at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:706)
> [ERROR] at com.google.gwt.dev.DevMode.main(DevMode.java:426)
> [ERROR] 2016-08-02 21:47:03.384:WARN:oejuc.AbstractLifeCycle:main: FAILED
> org.eclipse.jetty.server.handler.RequestLogHandler@17192bc:
> java.util.ServiceConfigurationError: org.apache.juli.logging.Log: Provider
> org.eclipse.jetty.apache.jsp.JuliLog not a subtype
>
