Closed iay closed 1 year ago
It may make sense to do this in two phases: Java 17 first, then Jakarta.
One aspect of the Java 17 (MDA 0.10, Shibboleth v17 parent) is that the java-support
module has been replaced with shib-support
, and the package names have changed. So it's not really possible to dodge this change in even the medium term.
Commit 908ff4213cf85d941d4d6b69e51f0cd72d12ee79 implements the Java 17 port. It overrides the JAXB versions we get from the new Shibboleth parent POM, so that we're still using the javax
namespaces and not jakarta
.
The Shibboleth MDA will be moving to the Shibboleth Java 17 platform as of 0.10, shortly upcoming. This includes changing from the old J2EE namespace to the new Jakarta one for things like JAXB.
This project needs to be updated for that environment. This involves a move to the new parent project, but we should also set up a maintenance branch as a matter of course.