Re: GWT 2.6.0 to 2.7.0 leads to compiler error 'java.lang.IncompatibleClassChangeError'
Thanks for the hint. It was an old ASM version.
Now it builds fine.
Am Mittwoch, 3. Dezember 2014 09:42:18 UTC+1 schrieb Cristiano:
Hi,
find out which dependency is including ASM and then try to exclude it in
your pom.xml
In our project, app-hmi-soaconnector was importing ASM as a
sub-dependency due to CXF, so It did added the exclusion tag like you can
see below directly in our main GWT web app project.
--- app_main/hmi/app-gwt-webapp/pom.xml (revision 7903)
+++ app_main/hmi/app-gwt-webapp/pom.xml (working copy)
@@ -130,6 +136,12 @@
artifactIdapp-hmi-soaconnector/artifactId
version${app.version}/version
+ exclusions
+ exclusion
+ artifactIdasm/artifactId
+ groupIdasm/groupId
+ /exclusion
+ /exclusions
/dependency
dependency
I found out the responsible using Eclipse Dependency Hierarchy.
Also remember to include codeserver dependency if you want to use super
dev mode
@@ -79,6 +79,12 @@
version${gwt.version}/version
scoperuntime/scope
/dependency
+ dependency
+ groupIdcom.google.gwt/groupId
+ artifactIdgwt-codeserver/artifactId
+ version${gwt.version}/version
+ scopetest/scope
+ /dependency
!-- Guice Injection dependencies --
dependency
groupIdcom.google.inject/groupId
Regards,
Cristiano
Il giorno Wed, 3 Dec 2014 alle 08:33 Thomas Broyer t.br...@gmail.com
javascript: ha scritto:
You must have an incompatible version of ASM in your build path. ASM only
ensures backwards compatible starting with version 4, earlier versions
should have been repackaged but it's not always the case (people have
listed Hibernate as a culprit for example)
--
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 javascript:.
To post to this group, send email to google-we...@googlegroups.com
javascript:.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
--
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/d/optout.
Re: Current state of one .js file per module
Ok, I'll try to use separated servers for code server and server side. Regarding the monolithic .js, in GWT 1.6 it was impossible to debug in both Chrome and Firefox - they both crashed, and I always suspected that the js / sourcemap file were too big. Now with GWT 2.7 I can debug normally in Chrome (didn't try in Firefox yet). Still I guess it could be faster to debug using separated .js files. However, as this is no longer GWT's goal, ok. At least now debugging in Chrome is usable, and I no longer need that old version of Firefox 26 which still runs the classic dev mode. Em sexta-feira, 5 de dezembro de 2014 12h31min41s UTC-2, Jens escreveu: Separate compilation mentioned in your linked issue has been reworked into incremental per file compilation what you have now with GWT 2.7. The benefit is that people do not have to refactor their applications into multiple modules to get the benefit of faster recompiles in SDM. Regarding CodeServer restarts: With current GWT master branch, a restart of the CodeServer reuses the caches from the last compile which reduces the startup time of CodeServer significantly. Keep in mind that you do not have to use the DevMode class to start the embedded Jetty + Code Server process. You can also split these processes so you do not have to restart SDM CodeServer if you do a server side change. DevMode -noserver or launching CodeServer directly only starts the SDM code server. Then you can provide your own application server or actually start DevMode -nosuperdevmode which does start classic DevMode but also the embedded Jetty for your server side code. I rarely restart CodeServer during the work day. -- J. -- 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/d/optout.
gwt 2.7.0 does not start in Chrome/39.0.2171.71: runtime user.agent value (unknown)
Hi, I have created a Hello World project with (gwt 2.7.0, but the same with gwt 2.6.0). I have tried it using google chrome. But the project does not start (with firefox works). The javascript console show the following error: Uncaught com.google.gwt.useragent.client.UserAgentAsserter$UserAgentAssertionError: Possible problem with your *.gwt.xml module file. The compile time user.agent value (safari) does not match the runtime user.agent value (unknown). Expect more errors. The user agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 There is a bug to detect chrome user agent at runtime? Any workaround? -- 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/d/optout.
Testing User Interface
I'd like to have some automated tests in my current GWT project for the user interface, things like when you click on a TextBox a popup dialog is shown when some options. I've tried using GQuery to check for elements in the RootPanel, but I can only see the elements that I have defined in an index.html but not the widgets that I bind later on the application. I read something about using Selenium but I needed to set a System property and in the GWTTestCase environment I can't access to System.setProperty(). Is there any way to do what I want? -- 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/d/optout.
Re: TabLayoutPanel - forcing onResize for unselected tab content
Hi, I think I found the problem. My TabLayoutPanel lives within a SplitLayoutPanel. Whenever I move the splitbars, I also change the size of the TabLayoutPanel. Then, all children are resized, too, These also include the tabs that are not visible, so the chess boards in these tabs are moved to (0.0). There are two problems here: - moving the split bars causes onResize for all tabs, including the invisible ones consequence: the boards are moved to (0,0), which increases flickering - the selection handler cannot resize the selected/visible tab immediately, but has to do the resizing in deferred code consequence: the board is visible at its wrong position for some milliseconds, which causes flickering Why do I need deferred code here? Can I avoid this, for example having a handler that is called when the real sizes are present? And if I cannot avoid deferred code, can I make supress repainting during the delay somehow? How would you do this? Magnus -- 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/d/optout.
[gwt-contrib] How to get the full StackTrace when using SuperDevMode in GWT 2.7?
I use GWT 2.7 with super dev mode. When it comes to an exception the stack trace looks like the following: SEVERE: UncaughtExceptioncom.github.nmorel.gwtjackson.client.exception.JsonDeserializationException: Unknown property 'uploadImageId' at Unknown.AHc_g$(Unknown Source) at Unknown.vHc_g$(Unknown Source) at Unknown.OHc_g$(Unknown Source) at Unknown.VHc_g$(Unknown Source) at Unknown.aIc_g$(Unknown Source) at Unknown.gIc_g$(Unknown Source) at Unknown.rDc_g$(Unknown Source) at Unknown.qDc_g$(Unknown Source) at Unknown.vNb_g$(Unknown Source) at Unknown.nNb_g$(Unknown Source) at Unknown.oNb_g$(Unknown Source) at Unknown.pNb_g$(Unknown Source) at Unknown.gNb_g$(Unknown Source) at Unknown.fNb_g$(Unknown Source) at Unknown.$Cc_g$(Unknown Source) at Unknown.ZCc_g$(Unknown Source) at Unknown.zOm_g$(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.ZDe_g$(Unknown Source) at Unknown.aEe_g$(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.anonymous(Unknown Source) at Unknown.anonymous(Unknown Source) *How can I get the full stack track deobfuscated with SuperDevMode?* -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/1cb2cb17-93b7-49d2-aeb6-56a37f43c21f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?
In my case it is a boolean, but not final, the value does change. Is there an optimisation that removes the field when it is false ? On Fri, Dec 5, 2014 at 6:41 PM, 'Roberto Lublinerman' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Yes,I meant (instance) final fields of primitive or string type initialized at declaration. Compile time constants are propagated by the compiler in draft and optimized mode. On Fri, Dec 5, 2014 at 8:49 AM, 'Ray Cromwell' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Static final fields on the prototype? I'm pretty sure these are promoted to global in optimized mode. Perhaps you meant final non-static fields? (which we should have an optimization for promoting to static :) ) On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: In draft compile Java compile time constants are emitted in the prototype. This should be exactly static final fields of primitive or string type assigned at declaration. This is the approach to compile time constants taken to implement Java semantics. FWIW in optimized compiles other fields might be upgraded to compile time constants. On Dec 5, 2014 2:18 AM, stuckagain david.no...@gmail.com wrote: I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG eclipse plugin. In the Chrome debugger I noticed that some fields are sometimes available under 'this' but sometimes they are available only in 'this.__proto__'. It seems that if I have a boolean field that is set to false that it does not appear in 'this' but under 'this.__proto__' and that I can not see it at all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to figure out how this works in GWT SuperDevMode. Another thing that takes getting used: list/map structures are not that easy to navigate anymore. I hope they found some way to make it easier to have some support to convert them to something readable in the debugger. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com . For more options, visit https://groups.google.com/d/optout. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7eTkVStPGXrtfiPk5kO8yr2gyjQCZY4xkAD5ufExWB_6g%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnaifVU5UEa7mU41UuRcEZvwp-NWv_6v5pHsq4Na%3D8uuQ%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnaifVU5UEa7mU41UuRcEZvwp-NWv_6v5pHsq4Na%3D8uuQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW1-qd9Cuq3bktppFqnQEykA0xiXFCmFeNJWf1W0d-_XYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
