Getting rid of Automatic Modules?

[EliasHeydrich]

Eclipse Collections, likely to support older Java versions, is not yet employing Java's module system. Therefore, an automatic module is created by the system, which will work just fine for 90% of the usecases.

A problem arises when trying to employ other elements of the modern Java Toolchain, such as JLink or JPackager. The former, for example, plainly refuses to work with automatic modules:

Error: automatic module cannot be used with jlink: org.eclipse.collections.impl from file:///C:/Users/{my-user}/.m2/repository/org/eclipse/collections/eclipse-collections/11.1.0/eclipse-collections-11.1.0.jar

Stackoverflow and other similar places suggest possible approaches, but these are hacky and involve either a lot of manual work or writing lots of build-system workarounds (like excluding Eclipse Collections at first, then adding it to the classpath later in form of a JAR)...

Is a "proper" module-info.java planned at some point? Note: Effectively, this is related to #1378.