elide-dev / jpms Goto Github PK

Library PRs

Beta Give feedback

1. feat: support jpms in annotations module google/j2objc#2302
   +0
2. Add module-info.java to checker-qual typetools/checker-framework#6326
   +0
   
3. feat: add jpms definition for annotations google/error-prone#4311
   +0
4. Guava + JPMS google/guava#7094
   P3 +1
5. feat: add jpms support with module-info.java Kotlin/kotlinx.collections.immutable#175
   +0
6. feat(jpms): add module-info.java descriptors reactive-streams/reactive-streams-jvm#556
   +0
7. feat(jpms): add module-info.java descriptors (w/build upgrades) reactive-streams/reactive-streams-jvm#557
   +0
8. feat: add support for jpms leangen/geantyref#29
   +0

Related Issues

Beta Give feedback

1. Add module descriptor typetools/checker-framework#4559
   +0
   
2. Add module-info.java google/error-prone#2649
   +0
3. Add Automatic-Module-Name to artifacts, particularly javac google/error-prone#1116
   +0
4. Cannot build Errorprone plugin with Jigsaw google/error-prone#1210
   +0
5. Add module-info.java google/guava#2970
   P3 package=general status=research type=enhancement +4
6. Migrate off of jsr305 google/guava#2960
   P3 status=triaged type=other +3
   
7. Provide module-info descriptor for java 9 and later Kotlin/kotlinx.collections.immutable#157
   request +1
8. Consider adding a full Java module descriptor reactive-streams/reactive-streams-jvm#531
   +0
9. Add a module-info.java protocolbuffers/protobuf#16133
   untriaged +1
10. Add module-info.java leangen/geantyref#28
    +0

In order to get some solid confidence going in the JPMS forks of these libraries, there is a spot in this repo for smoke tests and another for integration tests.

Right now, these roots are empty, but the intent is to fill them with:

• Smoke tests: jar --validate, and other obvious-failure tests; assertions about JAR structure, including valid MRJAR structure, illegal class layout, and so on. Loading libraries with a range of supported JDKs.

• Integration tests: Entire projects which depend on the libraries provided by this repo. Each is forked and overridden to depend on these libraries, or is instructed from outside the build to depend on these libraries based on configuration.

---

The question then moves naturally to a strong representative set of use of Guava, Reactive Streams, Protocol Buffers, and so on, from JVM languages.

• Projects which use Guava, Protobuf, and Reactive Streams
• Projects which use Guava + Protobuf
• Projects which use Guava or Protobuf

Example of results

Browsing and manually cross-referencing these lists, roughly ordered by stars and compatibility, yields (in vendor order):

• apache/dubbo - 39.9k stars, 26.2k forks, 3.1k watchers
• apple/pkl - 9k stars, 242 forks, 52 watchers
• bazelbuild/bazel - 22.1k stars, 3.9k forks, 605 watchers
• checkstyle/checkstyle - 8.1k stars, 3.6k forks, 223 watchers
• google/gson - 22.9k stars, 4.3k forks, 738 watchers
• line/armeria - 4.6k stars, 860 forks, 181 watchers
• NationalSecurityAgency/ghidra - 46.8k stars, 5.5k forks, 1k watchers
• pmd/pmd - 4.6k stars, 1.4k forks, 141 watchers
• signalapp/Signal-Server - 8.8k stars, 2.1k forks, 402 watchers

Comparison and reasoning below:

Repository	Build system + Language	Libraries used	Outcome
dubbo	Maven, Java	Protobuf, Guava, Reactive	✅ Included
pkl	Gradle, Java, Kotlin	Guava	✅ Included
bazel	Bazel, Java	Protobuf, Guava, Reactive	✅ Included
checkstyle	Maven, Java	Guava	✅ Included
gson	Maven, Java	Protobuf, Guava	🆙 Promoted
armeria	Gradle, Java	Guava, Protobuf, Reactive	✅ Included
ghidra	Gradle, Java	Guava, Protobuf	⚠️ Complex build
pmd	Maven, Java	Guava	✅ Included
Signal-Server	Maven, Java	Guava, Protobuf, Reactive	✅ Included

✅ = Included in integration tests
🆙 = Promoted to repository library
⚠️ = Problems or other blockers