JPMS modules
- Dominant language
- Java
- Stars
- 11.5k
- Forks
- 402
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 20
Description
While the artifacts currently contain `Automatic-Module-Name` declarations in the manifest, which should make them usable from other JPMS modules, they don't have an actual module-info, which is required to use them with jlink for example.
Instead of being automatic modules, at least the library artifacts should have support for being loaded as actual named modules.
(Unfortunately, the unmaintained patched ANTLR fork as well as the collections library you use appear to be incompatible with this though)
Contributor guide
Research direction
Start by inspecting the artifact build configuration and the generated manifests; the issue names no specific files or tests. Check how library artifacts could provide actual module-info descriptors, then verify compatibility with jlink and the patched ANTLR fork and collections library. Done means the relevant library artifacts work as named JPMS modules rather than only automatic modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100