Jakarta Mirgration, Eclipse Transformer and licenses

GeoServer GeoServer User
,
1

Hi, we are in the middle of a javaee → jakartaee migration.

Today, our team are running geoserver in a EE-container (TomEE). However, we want to migrate to the next version of EE.

To do so plan to make it simpler with the GitHub - eclipse/transformer: Eclipse Transformer provides tools and runtime components that transform Java binaries, such as individual class files and complete JARs and WARs, mapping changes to Java packages, type names, and related resource names., a gradle plugin that rewrites jars’ imports (search and replace javax.* → jakarta.*, based on a ruleset).

This is done as a part of the build chain. My question is how does this comply with your licencing.

2

Hi @BerntJulian and welcome to the user forum, glad you could join us here.

Thanks for looking ahead. Rewriting is fine - the result just ends up as GPL + EPL exception like the rest of GeoServer. The ability to use these tools is part of why we like free software.

The GeoServer project would also really like to migrate to the next version of EE (JakartaEE and Tomcat 10). For more information on the challenge see GeoServer 3 crowdfunding (and the Q&A section near the end with pictures). For our own GeoServer 3 planning we have focused on openrewrite but are keen to learn about your experience!

aside: The real goal here is not so much JakartaEE and Tomcat 10 as it is updating to spring-framework-6 and ensure GeoServer is operating in a supported environment.