-
Task
-
Resolution: Done
-
Major
-
None
-
None
Right now WildFly Core is still using pre-Jakarta EE 10 dependencies. All the relevant artifacts brought in from WildFly Core to WildFly full are overwritten in Full to use the expected dependencies. In addition, due to WFLY-16684, legacy dependencies brought by WildFly Core are already detached and also overwritten in Full.
That situation allows WildFly Core to move on and use Jakarta EE 10 dependencies on its distribution and test suite.
There is only one feature-pack in WildFly Core so we cannot use easily work on incremental steps to accomplish the migration, so this single Jira will be used for all the changes.
Some of the identified steps are:
- Add ee-10-api module to replace the ee-8-api used in core-feature-pack
- Use the Jakarta EE 10 expected dependencies for the test suite and build (jboss-invocation-jakarta, Undertow, elytron-integration)
- Migrate tests cases
After this change and once the WildFly Core release is merged on full we need to add a follow-up task to replace the overrides currently done on WildFly full and get let wildfly-core continue driving the dependencies
- is blocked by
-
WFLY-16787 Don't use jboss-invocation jboss-interceptors-api_1.2_spec dependencies from WildFly Core
- Closed
-
WFLY-16788 Move org.wildfly.security:wildfly-elytron-jaspi from testsuite/integration to the legacy modules
- Closed
-
WFLY-16841 Ensure javax.api JSONP is available on the test class path to bootstrap legacy kernel services
- Closed
- is related to
-
WFLY-16738 Replace the overridden dependencies that should be driven by WildFly Core
- Closed
- relates to
-
WFLY-16678 Post Big Bang follow ups
- Open
-
WFCORE-5939 Upgrade WildFly Elytron to 1.19.1.Final
- Resolved