On 14/01/2019 15:03, Scott Palmer wrote:
:
Does this not require ALL dependencies - down the entire dependency chain,
including every transitive dependency, to be 100% modular?
Look for "automatic modules", this is how the module system facilitates
top-down migration where you can migrate to modules without waiting
everything you depend on to migrate first. Automatic modules also
support bridging to the class path so you can migrate without moving
everything from the class path to module name.
I don’t know of many applications outside of those included in the JDK (where
dependencies are not an option) that this restriction actually applies to. In fact
since Java 11 there is a regression where applications that could be built as
modular with JDK 9 & 10 no longer can be, because the java.activation module
was removed and no modular replacement is available. Many dependency chains lead
to java.activation.
The JavaBeans Activation Framework (JAF) was always maintained as a
project in Java EE, never here. In any case, you can download JAF from
Maven and deploy it on the module path, it should just work. The only
issue with link time where it needs to be migrated to an explicit module
before it can be linked into a run-time image. There is an issue in its
Eclipse project to migrate it to an explicit module [1].
-Alan
[1] https://github.com/eclipse-ee4j/jaf/issues/13
