-
Notifications
You must be signed in to change notification settings - Fork 586
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting rid of Automatic Modules? #1451
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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.
The text was updated successfully, but these errors were encountered: