-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Now that WildFly is supported on modular JDKs only it is time to use standard JPMS modules.
Only Java SE aggregation module should be visible to all deployments by default.
JDK platform specific modules (JPMS modules starting with jdk.* prefix) are not available
on all JDKs and should be included into deployment explicitly by users on case by case basis.
The purpose of this PR is to minimize module path footprint for deployed applications
and to standardize deployments a bit.
- causes
-
WFCORE-6408 Add new DEPENDENCIES_JDBC_DRIVER phase for correct JDBC driver alignment
- Closed
-
WFLY-18158 Oracle JDBC driver deployed as deployment needs dependency on jdk.security.jgss module
- Closed
- incorporates
-
WFCORE-6237 Eliminate usage of deprecated javax.api module
- Closed
-
WFCORE-6245 Eliminate usage of deprecated ibm.jdk module
- Closed
-
WFCORE-6249 Eliminate usage of deprecated sun.jdk module
- Closed
-
WFCORE-6250 Don't include org.jboss.vfs module to all deployments by default
- Closed
-
WFCORE-6251 Eliminate usage of deprecated javax.xml.stream.api module
- Closed
-
WFLY-17909 Eliminate usage of deprecated ibm.jdk module
- Closed
-
WFLY-17931 Eliminate usage of deprecated javax.api module
- Closed
-
WFLY-17932 Eliminate usage of deprecated sun.jdk module
- Closed
-
WFLY-17933 Eliminate usage of deprecated javax.sql.api module
- Closed
-
WFLY-17934 Eliminate usage of deprecated javax.xml.stream.api module
- Closed
-
WFLY-17935 Move all distribution modules to latest schema namespace
- Closed
- is related to
-
WFCORE-3705 Allow dependencies on JDK modules
- Resolved