Ok I found the culprit!
It's the *gwt-bean-validators* library.
It's this particular commit:
https://gitlab.com/ManfredTremmel/gwt-bean-validators/-/commit/da32e4003f6a55b12a3ac16cae7576b80e6749fd
They force the safari permutation for every browser:
I can workaround it by updating my Module
Hi,
So I upgraded our app from GWT 2.8.2 to 2.9.0 and I'm facing an issue with
Firefox (it's a GXT 4.0.3 app but I don't think it's relevant in this issue)
It throws an Exception:
Possible problem with your *.gwt.xml module file.The compile time
> user.agent value (safari) does not match the
I sincerely appreciate that you're trying to offer advice about this,
Thomas, especially in the middle of the night where you are, but it's hard
to imagine a non-Eclipse user fully understanding what I'm describing here.
Is there nobody who still works on GWT who knows about Eclipse and the GWT
Disclaimer: I'm not an Eclipse user.
Your problem is that Eclipse flags issues that will only happen if you use
the modulepath (which I would say, in an IDE, would mean "if the project is
configured to produce a JPMS module"); using the classpath still works. So
if Eclipse has a way to say
What exception?
If you're seeing error messages in the general format "The package
org.w3c.dom is accessible from more than one module: , java.xml"
when you build your GWT project with Java 11, then it's the same issue I
described here.
On Monday, May 18, 2020 at 1:53:49 PM UTC-7, Dr. Lofi
I have general the problem: Using OpenJDK 11 with my latest Eclipse
2020-03. It always gives me an exception, so that I could not use JDK 11
with my latest Eclipse.
Therefore I still use JDK 8 to run my Eclipse 2020-03... I haven't got any
time to search why...
Thanks,
Lofi
Am Montag, 18.
You lost me there, Thomas. I'm not trying to directly interact with
gwt-dev.jar; I'm just pointing Eclipse to a GWT SDK, the same way I've been
doing for years. Are you saying that standard GWT SDKs are now considered
to be incompatible with Eclipse? If that's the situation, is it documented
The gwt-dev.jar from the ZIP distribution is an uber-jar with all
dependencies needed to run GWT (so you only need gwt-dev.jar and
gwt-user.jar in your classpath, and any third-party dependency you're
using), so this is expected.
Use gwt-dev from the Central Repository (aka Maven Central)
I struggled with a module-related issue a year ago when I tried to
configure an Eclipse 2019-03 + Java 11 build environment with a project
that includes GWT 2.8.2. These are my testing notes from the time:
Updating a working Java 11 build environment from Eclipse 2018-12 to
2019-03 introduced
Thanks for your reply. I do see CodeServer.class on my gwt-dev-2.9.0.jar on
my local repo, so not sure why it isn't finding it.
And I'm using mvn version 3.6.3, so not sure why it isn't using the SSL
version of the repo url. Used both java 8 and 13 to see if there is any
difference but couldn't
Awesome news!
Michael
On Thursday, May 14, 2020 at 5:40:25 AM UTC+2, Colin Alworth wrote:
>
> Today we are pleased to announce the next release of GWT, version 2.9.0.
> Some highlights of this release:
> * GWT supports Java 9, 10, 11 language features.
> * The elemental2 1.0.0 release is
11 matches
Mail list logo
