Thursday, October 24, 2024

Embedded Jars and Java 17

I've been working on a project for a while (posted a related problem some time back) to convert our massively complex software from Java 8 to Java 17.

Almost everything is done, but a recurring problem, one that just reared its head again this morning, as to do with jar conflicts.  [I am so angry with the Java architects for "fixing" the version problem in such an intractable, unmanageable way...]

The problem occurs when another jar (in this case gwt-dev.jar) embeds other class files (in this case org.apache.commons.io) that are otherwise used in our software.

Some questions:

1) What version of commons-io is it within gwt-dev.jar?
2) Is it all of the classes, or only the classes needed/referenced by gwt-dev code?
3) Has anyone else had this problem and found a good solution?

Approaches I am going to try are:

1) Match our commons IO version to the one in gwt-dev (this bothers me, because there may be a lot of recoding on my end) and remove the commons-io jar from our classpath.
2) If that doesn't work, then also rebuild the gwt-dev jar without the commons-io (this won't work until I match our commons IO version to the one gwt-dev.jar embeds).
3) Beg you to solve this problem for me somehow.

--
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/b2259293-b34e-48bb-9ae7-22425ebb9d69n%40googlegroups.com.

No comments:

Post a Comment