GWT 2.8 compile fails; 2.7 works
In our app, we have a UiBinder widget (SomeViewImpl) which has, as its root
element, a widget which itself is a UiBinder widget
(CollectionManagementLayout).
My UiBinder declaration in SomeViewImpl looks like this:
interface CollectionManagementPanelUiBinder extends
UiBinder {}
The UiBinder XML for the SomeViewImpl class starts off like this:
. . .
This code compiles just fine in GWT 2.7, but with 2.8, I get the following
error:
[ERROR] Errors in
'generated://09CDEAB17C92C8C75AB00C9F2F0DF847/com/myco/myproduct/client/stuff/collections/SomeViewImpl_CollectionManagementPanelUiBinderImpl.java'
[ERROR] Line 17: The interface UiBinder cannot be implemented more
than once with different arguments:
UiBinder and
UiBinder
See snapshot:
/tmp/com.myco.myproduct.client.stuff.collections.SomeViewImpl_CollectionManagementPanelUiBinderImpl3472216513944602205.java
Tracing compile failure path for type
'com.myco.myproduct.client.stuff.collections.SomeViewImpl_CollectionManagementPanelUiBinderImpl'
[ERROR] Errors in
'generated://09CDEAB17C92C8C75AB00C9F2F0DF847/com/myco/myproduct/client/stuff/collections/SomeViewImpl_CollectionManagementPanelUiBinderImpl.java'
[ERROR] Line 17: The interface UiBinder cannot be implemented more
than once with different arguments:
UiBinder and
UiBinder
The generated code looks like this:
public class SomeViewImpl_CollectionManagementPanelUiBinderImpl
implements UiBinder,
SomeViewImpl.CollectionManagementPanelUiBinder {
I worked around this by changing the UiBinder declaration in SomeViewImpl
to be:
interface CollectionManagementPanelUiBinder extends UiBinder {}
*My question is*: Should this have failed in GWT 2.7? Or is there a bug in
GWT 2.8?
thanks,
jay
--
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: Internal GWT 2.8.0 compiler exception
Yes, that was it. lib-gwt-svg was the wrong version. Thank you for the pointer! jay On Wednesday, November 16, 2016 at 9:41:13 AM UTC-8, jgindin wrote: > > I'm trying to update my project from GWT 2.7.0 to 2.8.0. However, I'm > getting the following error during the GWT compilation. > > We're using dagger and guava 20. I've validated that: > >- dagger-compiler is *NOT* in the classpath when compiling. (We're >using gradle and the "net.ltgt.apt" gradle plugin to use the "apt" >configuration (which is where the dagger-compiler dependency is listed). >- there are no gwt 2.7 artifacts in my classpath > > > > > > Thanks in advance for any help > > jay > -- 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.
Internal GWT 2.8.0 compiler exception
I'm trying to update my project from GWT 2.7.0 to 2.8.0. However, I'm getting the following error during the GWT compilation. We're using dagger and guava 20. I've validated that: - dagger-compiler is *NOT* in the classpath when compiling. (We're using gradle and the "net.ltgt.apt" gradle plugin to use the "apt" configuration (which is where the dagger-compiler dependency is listed). - there are no gwt 2.7 artifacts in my classpath Starting process 'command '/opt/devtools/java/jdk1.8.0_102/bin/java''. Working directory: /home/myusername/src/mycompany/myproduct/ui/studio Command: /opt/devtools/java/jdk1.8.0_102/bin/java -Xmx2g -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /home/myusername/.gradle/caches/modules-2/files-2.1/com.google.guava/guava-gwt/20.0/a77ac8a237301c629e3304c3cb3e2d540e79d0a8/guava-gwt-20.0.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-dev/2.8.0/f160a61272c5ebe805cd2d3d3256ed3ecf14893f/gwt-dev-2.8.0.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.code.findbugs/jsr305/1.3.9/40719ea6961c0cb6afaeb6a921eaa1f6afd4cfdf/jsr305-1.3.9.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.errorprone/error_prone_annotations/2.0.12/8530d22d4ae8419e799d5a5234e0d2c0dcf15d4b/error_prone_annotations-2.0.12.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.j2objc/j2objc-annotations/1.1/976d8d30bebc251db406f2bdb3eb01962b5685b3/j2objc-annotations-1.1.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/20.0/89507701249388e1ed5ddcf8c41f4ce1be7831ef/guava-20.0.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.google.code.gson/gson/2.6.2/f1bc476cc167b18e66c297df599b2377131a8947/gson-2.6.2.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.ow2.asm/asm/5.0.3/dcc2193db20e19e1feca8b1240dbbc4e190824fa/asm-5.0.3.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.ow2.asm/asm-util/5.0.3/1512e5571325854b05fb1efce1db75fcced54389/asm-util-5.0.3.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.ow2.asm/asm-commons/5.0.3/a7111830132c7f87d08fe48cb0ca07630f8cb91c/asm-commons-5.0.3.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/colt/colt/1.2.0/abc984f3adc760684d49e0f11ddf167ba516d4f/colt-1.2.0.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/ant/ant/1.6.5/7d18faf23df1a5c3a43613952e0e8a182664564b/ant-1.6.5.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/commons-collections/commons-collections/3.2.2/8ad72fe39fa8c91eaaf12aadb21e0c3661fe26d5/commons-collections-3.2.2.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/commons-io/commons-io/2.4/b1b6ea3b7e4aa4f492509a4952029cd8e48019ad/commons-io-2.4.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/com.ibm.icu/icu4j/50.1.1/c1267563fd08f2885bc1f934ddaca15d19c3d888/icu4j-50.1.1.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/tapestry/tapestry/4.0.2/e855a807425d522e958cbce8697f21e9d679b1f7/tapestry-4.0.2.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/net.sourceforge.htmlunit/htmlunit/2.19/230f011fa87e96ff4115cd8c9d1572572d718b3e/htmlunit-2.19.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-webapp/9.2.14.v20151106/773f1c45f6534bff6313997ab3bdbe25533ee255/jetty-webapp-9.2.14.v20151106.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-servlets/9.2.14.v20151106/a75c78a0ee544073457ca5ee9db20fdc6ed55225/jetty-servlets-9.2.14.v20151106.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-annotations/9.2.14.v20151106/bb7030e5d13eaf9023f38e297c8b2fcae4f8be9b/jetty-annotations-9.2.14.v20151106.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/apache-jsp/9.2.14.v20151106/756745c6efff964ae8d183866b962a534f20e30/apache-jsp-9.2.14.v20151106.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.ow2.asm/asm-tree/5.0.3/287749b48ba7162fb67c93a026d690b29f410bed/asm-tree-5.0.3.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/xalan/xalan/2.7.2/d55d3f02a56ec4c25695fe67e1334ff8c2ecea23/xalan-2.7.2.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-lang3/3.4/5fe28b9518e58819180a43a850fbc0dd24b7c050/commons-lang3-3.4.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.apache.httpcomponents/httpclient/4.5.1/7e3cecc566df91338c6c67883b89ddd05a17db43/httpclient-4.5.1.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/org.apache.httpcomponents/httpmime/4.5.1/96823b9421ebb9f490dec837d9f96134e864e3a7/httpmime-4.5.1.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/net.sourceforge.htmlunit/htmlunit-core-js/2.17/4316d68f449d42f69faf4ee255aa31b03e4f7dd5/htmlunit-core-js-2.17.jar:/home/myusername/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.11.0
Re: Measuring effect of using GWT features on compile time
Yes, but as you pointed out, that's no longer going to work ;-) On Thursday, June 9, 2016 at 10:22:47 AM UTC-7, Thomas Broyer wrote: > > Isn't DashboardNotifier called by SpeedTracerLogger? -- 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: Measuring effect of using GWT features on compile time
FWIW, as far as I can tell, the DashboardNotifier is *only* notified when dev mode starts and stops via com.google.gwt.dev.util.log.dashboard.DashboardNotifier#devModeSessionBegin and com.google.gwt.dev.util.log.dashboard.DashboardNotifier#devModeSessionEnd. I can't find anywhere in the GWT code base that uses the devModeEventBegin/End methods. I wound up just digging through the DEBUG output to get the answer I needed. For that I am appreciative of the pointer. It was not as hard as I was expecting since I could easily search for the lines I needed to find. Thank you. jay On Wednesday, June 8, 2016 at 3:05:23 AM UTC-7, Thomas Broyer wrote: > > > > On Wednesday, June 8, 2016 at 1:50:03 AM UTC+2, jgindin wrote: >> >> I'm looking for some way to see how much of my GWT compile time is coming >> from our usage of different features. Specifically: >> >>- UiBinder >>- RPC >>- Guice (not core GWT, I know...but maybe there's a way to see this >>too) >> >> >> For RPCs in particular, I've tried to dig around and see if there are any >> "hidden" flags, but have come up empty handed so far. >> >> Does anyone know of some way to find this information? (I'm using GWT >> 2.7...) >> > > You'll get timing information for each generator invocation when you set > the log level to DEBUG, but it won't be easy to parse. > But there are hidden flags (as system properties) to enable performance > logging; e.g. -Dgwt.speedtracerlog=/path/to/file.html (but this requires > the SpeedTracer extension for Chrome, which is no longer maintained > –probably no longer works– and has been removed from the Chrome Web Store), > or -Dgwt.dashboard.notifierClass=xxx (where xxx is the name of a class > implementing com.google.gwt.dev.util.log.dashboard.DashboardNotifier). That > last one is what (I believe) Google is currently using internally. You'll > get specialized events for UiBinder, RPC and GIN (and I18N), and a generic > event for other generators. (you'll find -Dgwt.perflog and > -Dgwt.perfcounters but I don't think they produce anything nowadays) > -- 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.
Measuring effect of using GWT features on compile time
I'm looking for some way to see how much of my GWT compile time is coming from our usage of different features. Specifically: - UiBinder - RPC - Guice (not core GWT, I know...but maybe there's a way to see this too) For RPCs in particular, I've tried to dig around and see if there are any "hidden" flags, but have come up empty handed so far. Does anyone know of some way to find this information? (I'm using GWT 2.7...) Thanks, Jay -- 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: IE11
The issues noted by Thomas are exactly those which are causing us problems right now, and will impact some of our significant customers / partners. I'm digging into what exact issues come up once we're able to force the GWT bootstrap process to download the IE9 permutation (instead of the FF permutation, which truly does not work). Can someone from Vaadin chime in as to the state of the IE 10/11 support will be in GWT 2.6? Thanks, Jay On Monday, September 9, 2013 2:42:20 AM UTC-7, Thomas Broyer wrote: > > > > On Monday, September 9, 2013 11:16:27 AM UTC+2, stuckagain wrote: >> >> Thomas, >> >> What are the known issues ? We have been running our apps for quite some >> time on IE10 (build with 2.4.0 and 2.5.1) with nothing really blocking. >> Does it hurt that we target IE=edge ? Should we really set IE9 as >> document version ? >> > > According to > https://code.google.com/p/google-web-toolkit/issues/detail?id=8063, IE10 > should work OK with the ie9 permutation in its "IE10 Standards" mode. I > think "proper support" here mostly means "new features" (such as > TypedArrays and pointer events). > > I have no idea what would be needed for IE11 though (but see > https://code.google.com/p/google-web-toolkit/issues/list?can=2&q=ie11) > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
IE11
I'm hoping someone can comment on getting full-fledged support for IE11 into GWT 2.6. I seem to remember that Vaadin was taking the lead on this, but the link I had to a Google Doc with the GWT Road Map is now a protected link. IE 11 support is a **huge** deal for us, and it's due to be out in GA in just over a month... Thanks in advance for the updates, Jay -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
JavaDocs are out of date?
Any chance someone can update the JavaDocs at http://google-web-toolkit.googlecode.com/svn/javadoc/latest/index.html? The header says these docs are for GWT 2.5.0.*rc2*. I don't actually know if that's true, or if there's just a typo, but it'd be more re-assuring if the header was 2.5.1... FWIW, this link is available from https://developers.google.com/web-toolkit/doc/latest/RefGWTClassAPI. Thanks, jay -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: CappuccinoGWT
I'm quite interested, especially in the dual-handle slider widget. Under which license are you providing this code? jay -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/xF5yr9rqGaUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
