Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "MicroProfile/JDK11Runtime"
Line 9: | Line 9: | ||
| Context Propagation || No || No | | Context Propagation || No || No | ||
|- | |- | ||
− | | Fault Tolerance || | + | | Fault Tolerance || 2.0 || 2.0 |
|- | |- | ||
| Health || No || No | | Health || No || No |
Revision as of 13:24, 1 October 2019
This page is intended to track the status of each MicroProfile specification as it moves towards JDK 11 runtime compatibility.
Specification | Spec Binary and TCK Compat | Spec Binary TCK Source |
---|---|---|
Config | No | No |
Context Propagation | No | No |
Fault Tolerance | 2.0 | 2.0 |
Health | No | No |
JWT | No | No |
Metrics | 2.1 | 2.1 |
Open Tracing | No | No |
Open API | No | No |
Reactive Messaging | No | No |
Reactive Streams Operators | No | No |
REST Client | No | No |
Note: Specifications should switch "No" to the version of the specification that complies with each of the Architectural issues when it's done
Comment from Payara:
All the MP TCKs except OpenTracing pass with Payara on JDK 11. It applies to the following versions:
- Config 1.3
- Fault Tolerance 2.0
- Health 1.0
- JWT Auth 1.1
- Metrics 2.0
- OpenAPI 1.0
- Rest Client 1.1
OpenTracing 1.3 passes on Payara with JDK 8 but some tests fail on JDK 11. It's not yet confirmed if the issue comes from the TCK or from Payara. The TCKs are built on JDK 8 in both cases, we haven't tried building them on JDK 11.