[wildfly-dev] Re: Deprecated Modules Cleanup + Standardized Deployments

[0] https://en.wikipedia.org/wiki/Java_version_history - Java release dates > [1] https://issues.redhat.com/browse/MODULES-254 - Support for >>>>> dependency on Jigsaw modules from static modules >>>>> [2] https://issues.redhat.com/browse/WFCORE-3705 - Allow >>>>> dependencies on JDK modules >>>>> [3] https://issues.redhat.com/browse/WFCORE-3684 - Upgrade JBoss >>>>> Modules to 1.8.0.Final >>>>> [4] https://issues.redhat.com/browse/WFCORE-6248 - Only Java SE >>>>> aggregation module should be visible to all deployments by default >>>>> [5] https://openjdk.org/jeps/200 - JEP 200: The Modular JDK >>>>> [6] https://issues.redhat.com/browse/WFCORE-6237 - Eliminate usage >>>>> of deprecated javax.api module >>>>> [7] https://issues.redhat.com/browse/WFCORE-6245 - Eliminate usage >>>>> of deprecated ibm.jdk module >>>>> >>>> [8] https://issues.redhat.com/browse/WFCORE-6249 - Eliminate usage of >>>>> deprecated sun.jdk module >>>>> >>>> @Richard Opalka <ropalka(a)redhat.com&gt; , notice we plan to release WildFly Core 20.0.0.Final tomorrow, so there is still a chance to get this cleanup done for WildFly 28, if you want to get this one also in we would need a PR today. > [9] https://issues.redhat.com/browse/WFCORE-6250 - Don't include >>>>> org.jboss.vfs module to all deployments by default >>>>> [10] https://issues.redhat.com/browse/WFLY-17666 - Deployments using >>>>> RMI Java Naming provider must define explicit dependency on jdk.naming.rmi >>>>> JPMS module >>>>> >>>> >