-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GWT 2.9 has dependancies which are not supported in latest Java versions. #9750
Comments
I made a release that may fix your issues:
https://www.icoa.com/gwt-with-jetty-9-4/
…On Fri, Jan 21, 2022 at 5:58 AM Nick Nikolaev ***@***.***> wrote:
*GWT version:* 2.9
*Browser (with version):* Chrome (latest)
*Operating System:* Windows Server 2016
------------------------------
Description
Hello mates,
Me and my colleagues are bumping our existing project from java 8 to java
16, later to 17 (due yet unsupported libs/plugins, etc.).
And today we hit a problem with the ASM, the lib which comes with GWT 2.9
is version 7.1 (from 2019), which supports up to Java 13 - the latest
version is 9.2.
Can I kindly request for a bump. As well probably and other dependencies
will need to be updated in order to support the latest Java LTS version -
17.
Steps to reproduce
Use Java 17.
Known workarounds Links to further discussions
—
Reply to this email directly, view it on GitHub
<#9750>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAOILH4OJKM4VAZRBXFPVTUXE33VANCNFSM5MPGR2YQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hello Shawn, Thank you for the quick answer, but we cannot use private projects/repos. Into the maven POM, we have tried to exclude bundled extension ASM 7.1 and then include the new version 9.2 as dependency, but then another lib -> Typostry "blow's up" ( java.lang.NoClassDefFoundError: org/apache/tapestry/util/text/LocalizedProperties) - they also use ASM as dependency and they have introduce support for ASM 9.2 in the latest version 5.8.0. So some more general solution will be needed. |
There is a patch under review right now (it has been +2'd, but I haven't had the chance to return to it to finalize it) which updates to latest Jetty 9.4, and asm 9.2. With that said, can you confirm that you are specifically failing when trying to run your server app inside GWT's dev mode? If so, this is not encouraged (and the jetty/asm updates are to allow htmlunit to be made more recent, not to target your use case) - it is far better to run your own server, and to run DevMode/CodeServer separately, with the -war/-launchDir argument to build JS where your usual server can see it, and provide it to the browser. That guarantees that problems like this or jetty specific configuration issues cannot affect you. See also: From that last link, try adding https://repo.vertispan.com/gwt-snapshot/ as a maven repository, and use gwt version 2.10.0-htmlunit-upgrade-SNAPSHOT. This might be slightly out of date at this point, but still includes a very recent jetty/asm. |
Hello Colin, Thanks for very much for you answer as well. Still... work in progress. You have done a lot of work as I saw the commits here. Good job! Hope to see new GWT version soon. |
@wrbst if you're having other issues outside of the jetty version, can you file a new issue? GWT 2.10 will be released in the next few days, marking this as closed. |
GWT version: 2.9
Browser (with version): Chrome (latest)
Operating System: Windows Server 2016
Description
Hello mates,
Me and my colleagues are bumping our existing project from java 8 to java 16, later to 17 (due yet unsupported libs/plugins, etc.).
And today we hit a problem with the ASM, the lib which comes with GWT 2.9 is version 7.1 (from 2019), which supports up to Java 13 - the latest version is 9.2.
Can I kindly request for a bump. As well probably and other dependencies will need to be updated in order to support the latest Java LTS version - 17.
Steps to reproduce
Use Java 17.
Known workarounds
Links to further discussions
The text was updated successfully, but these errors were encountered: