Hi all,
I'm migrating all my GWT apps to 2.7.0.
For one of these i've got this strange exception appearing quickly:
java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.BytecodeSignatureMaker$CompileDependencyVisitor
has interface org.objectweb.asm.ClassVisitor as super class
Hi Jens,
Thank you so much.
It was exactly that !
Moreover, I've got to admit that I don't think I'd have ever found this out
by myself.
Thank you again.
François
2014-11-19 17:45 GMT+01:00 Jens jens.nehlme...@gmail.com:
GWT 2.7. requires ASM 5.x (because of Java8 support in the future) and
Hi Thomas,
Thanks for your answer.
Here is a stackoverflow post (december 2011) which points on the freezing
problem I was encoutering at this time
(http://stackoverflow.com/questions/8564872/maven-project-builder-is-invoked-every-time-i-change-a-source-file-gwt).
The proposed answer was to
Hi,
Two years ago when I started working with GWT, I tried to use Eclipse and
M2E on my projects but M2E was regularly launching full builds of the
application which froze Eclipse for long periods.
At this moment I've found Daniel Kurska's article
Hi all,
I'm migrating from 2.5.1/Classical Dev Mode to 2.7.0-RC1/Super Dev Mode.
I'm really exited about new features.
But (yes, there is a but...) although I easily launch in SDM the basic
project generated by Eclipse, It doesn't work with my real project:
I launch it from Eclipse : everything
exiting !
Thanks
François
Le mardi 4 novembre 2014 12:18:56 UTC+1, Francois ANDRE a écrit :
Hi all,
I'm migrating from 2.5.1/Classical Dev Mode to 2.7.0-RC1/Super Dev Mode.
I'm really exited about new features.
But (yes, there is a but...) although I easily launch in SDM the basic
Hi,
I've had the same issue with gwt-openLayers and DialogBox.
The solution I've found was to force the dialogBox z-Index to a high value:
final DialogBox box = new DialogBox();
box.getElement().getStyle().setProperty(zIndex, );
It has worked for me.
François
Le lundi 15 décembre 2008
