I'm working on preparing a release branch for the upcoming 2.0.1 release and found some issues with our dependencies.
Most of the Jakarta EE API dependencies in the core module are compile instead of provided-scoped. I guess this was done by mistake during the namespace migration.
The testsuite and the ext modules are still using the Jakarta EE 8 API (javax.* version). I guess this didn't cause any problems, because we pull in the individual spec JARs in the correct version as well via some transitive path.
The core module has a compile-scoped dependency on the MVC API. We did this intentionally back then, but I guess it is time to change this and use provided scope as for all other APIs.
I ran the TCK for Glassfish and Wildfly locally and everything works fine.
Please note that I'll prepare a separate pull request in the next days to add a <dependencyManagement> section to the parent pom to unify the overall dependency handling which is quite confusing at the moment. But I want to get a quick fix in ASAP so we can cherry-pick it into the 2.0.1 release branch.
I'm working on preparing a release branch for the upcoming 2.0.1 release and found some issues with our dependencies.
coremodule arecompileinstead ofprovided-scoped. I guess this was done by mistake during the namespace migration.testsuiteand theextmodules are still using the Jakarta EE 8 API (javax.*version). I guess this didn't cause any problems, because we pull in the individual spec JARs in the correct version as well via some transitive path.coremodule has acompile-scoped dependency on the MVC API. We did this intentionally back then, but I guess it is time to change this and useprovidedscope as for all other APIs.I ran the TCK for Glassfish and Wildfly locally and everything works fine.
Please note that I'll prepare a separate pull request in the next days to add a
<dependencyManagement>section to the parent pom to unify the overall dependency handling which is quite confusing at the moment. But I want to get a quick fix in ASAP so we can cherry-pick it into the 2.0.1 release branch.