jakartaee / jakartaee/platform
Clarify JPMS requirements on platform Wiki across all runtimes, EE, SE, ...
- Dominant language
- No language data
- Stars
- 230
- Forks
- 77
- Avg merge
- 8d 5h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
The [Modularized Jars](https://github.com/eclipse-ee4j/jakartaee-platform/wiki/Modularized-Jars) page on the wiki only talks about "Jakarta EE run-times" support of JPMS. The question was raised about Java SE based run modes as well since there are several specs that support usage in such environments.
**Describe the solution you'd like**
The wiki page should be updated for the common platform expectations across all runtime modes.
**Additional context**
There is a Jakarta Activation [challenge](https://github.com/eclipse-ee4j/jaf/issues/98) regarding assumptions about the TCK being able to use JPMS and further questions on whether there should be different behaviors when running under a EE container runtime vs a Java SE environment.
[AB#67](https://dev.azure.com/jakarta-ee-azdo/7cf9a9d3-9854-41e0-9a66-99506a9ed874/_workitems/edit/67)
Contributor guide
Research direction
Start with the Modularized Jars page on the platform Wiki, then read the linked Jakarta Activation challenge in jaf#98 for the JPMS and runtime-mode questions. Compare the documented expectations for Jakarta EE runtimes with Java SE-based modes and update the page to cover the common expectations across all runtime modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100