No presence of module-info.class within SDK jars
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 243
- Forks
- 171
- Avg merge
- 30m
- Merged PRs (30d)
- 4
Description
While checking OCI SDK v2.41.0 - I don't see presence of module-info.class within jars like oci-java-sdk-common-2.41.0.jar. And no presence of Automatic-Module-Name: <module name> within MANIFEST.MF as well.
And so from JDK17 usage perspective - such is then treated as automatic modules with everything exported. Any plans to make them to be instead named modules with mostly export of public APIs/classes/interfaces?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the OCI SDK v2.41.0 JARs, including oci-java-sdk-common-2.41.0.jar, and their MANIFEST.MF files under JDK 17. Determine the scope for adding named-module metadata and limiting exports, then verify the resulting artifacts behave as intended for JDK 17 consumers.
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