diff --git a/pom.xml b/pom.xml index 95ea686..8d6e491 100644 --- a/pom.xml +++ b/pom.xml @@ -107,14 +107,14 @@ 10.0.0 - 3.1-RC2 + 3.1 4.0.2 4.0.1 - 5.1.0-RC1 + 5.1.0 2.1 - 3.1 + 3.1.1 3.0.1 - 1.1-RC2 + 1.1 diff --git a/spec/src/main/asciidoc/architecture.adoc b/spec/src/main/asciidoc/architecture.adoc index 27671a2..43bdcbd 100644 --- a/spec/src/main/asciidoc/architecture.adoc +++ b/spec/src/main/asciidoc/architecture.adoc @@ -28,13 +28,12 @@ Core Profile or the Cloud Native Computing Foundation (like OpenTelemetry), or they are component specifications of the MicroProfile project (such as Config). Since the MicroProfile repo is an "umbrella" project, no individual API or TCK is generated for this specification. -This specification documents the component specification contents of each release. +This specification documents the component specification contents of each release. An implementation can use later patch releases of component specifications. The specifications for each release are listed in reverse chronological order. -[[microprofile6.0]] -=== MicroProfile 6.1-RC1 - +[[microprofile6.1]] +=== MicroProfile 6.1 Based on MicroProfile's time-boxed release process, this is a minor release that does not include backward incompatible changes. Like MicroProfile 6.0, this release requires Jakarta EE Core Profile 10. If you are still dependent on Jakarta EE 9.1, please consider using the https://github.com/eclipse/microprofile/releases/tag/5.0[5.0 release of MicroProfile]. @@ -45,12 +44,12 @@ If you are still dependent on Java EE 7, please consider using the https://githu The complete list of MicroProfile 6.1 specifications includes: * https://jakarta.ee/specifications/coreprofile/10/[Jakarta EE 10 Core Profile] -* https://github.com/eclipse/microprofile-config/releases/tag/3.1-RC2[MicroProfile Config 3.1] +* https://github.com/eclipse/microprofile-config/releases/tag/3.1[MicroProfile Config 3.1] * https://github.com/eclipse/microprofile-fault-tolerance/releases/tag/4.0.2[MicroProfile Fault Tolerance 4.0] -* https://github.com/eclipse/microprofile-metrics/releases/tag/5.1.0-RC1[MicroProfile Metrics 5.1] +* https://github.com/eclipse/microprofile-metrics/releases/tag/5.1.0[MicroProfile Metrics 5.1] * https://github.com/eclipse/microprofile-health/releases/tag/4.0.1[MicroProfile Health 4.0] -* https://github.com/eclipse/microprofile-telemetry/releases/tag/1.1-RC2[MicroProfile Telemetry 1.1] -* https://github.com/eclipse/microprofile-open-api/releases/tag/3.1[MicroProfile OpenAPI 3.1] +* https://github.com/eclipse/microprofile-telemetry/releases/tag/1.1[MicroProfile Telemetry 1.1] +* https://github.com/eclipse/microprofile-open-api/releases/tag/3.1.1[MicroProfile OpenAPI 3.1] * https://github.com/eclipse/microprofile-jwt-auth/releases/tag/2.1[MicroProfile JWT Authentication 2.1] * https://github.com/eclipse/microprofile-rest-client/releases/tag/3.0.1[MicroProfile Rest Client 3.0] @@ -60,14 +59,15 @@ The Maven coordinates for this Eclipse release are as follows: org.eclipse.microprofile microprofile - 6.1-RC1 + 6.1 pom provided ---- -Here is the link to https://github.com/eclipse/microprofile/releases/tag/6.1-RC1[the github repository] for this Eclipse-based project. +Here is the link to https://github.com/eclipse/microprofile/releases/tag/6.1[the github repository] for this Eclipse-based project. +[[microprofile6.0]] === MicroProfile 6.0 MicroProfile 6.0 replaces required individual Jakarta specifications in prior releases like Jakarta Restful Web Services and JSON Binding with the Jakarta EE 10 Core Profile. diff --git a/spec/src/main/asciidoc/required-apis.adoc b/spec/src/main/asciidoc/required-apis.adoc index 9c10bf4..286c034 100644 --- a/spec/src/main/asciidoc/required-apis.adoc +++ b/spec/src/main/asciidoc/required-apis.adoc @@ -67,7 +67,7 @@ pass:[**] Full CDI support is not required. CDI SE support is not required. MicroProfile Config provides applications and microservices means to obtain configuration properties through several environment-aware sources both internal and external to the application and made available through dependency injection or lookup. * https://microprofile.io/project/eclipse/microprofile-config -* https://github.com/eclipse/microprofile-config/releases/tag/3.1-RC2 +* https://github.com/eclipse/microprofile-config/releases/tag/3.1 [[mp-fault-tolerance]] === MicroProfile Fault Tolerance 4.0 @@ -102,7 +102,7 @@ MicroProfile Metrics provides a unified way for MicroProfile applications to exp Metrics will also provide a common Java API for exposing their telemetry data. * https://microprofile.io/project/eclipse/microprofile-metrics -* https://github.com/eclipse/microprofile-metrics/releases/tag/5.1.0-RC1 +* https://github.com/eclipse/microprofile-metrics/releases/tag/5.1.0 [[mp-open-api]] === MicroProfile OpenAPI 3.1 @@ -110,10 +110,10 @@ Metrics will also provide a common Java API for exposing their telemetry data. MicroProfile OpenAPI provides a unified Java API for the https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md[OpenAPI v3 specification] that all application developers can use to expose their API documentation. * https://microprofile.io/project/eclipse/microprofile-open-api -* https://github.com/eclipse/microprofile-open-api/releases/tag/3.1 +* https://github.com/eclipse/microprofile-open-api/releases/tag/3.1.1 [[mp-telemetry]] -=== MicroProfile Telemetry 1.0 +=== MicroProfile Telemetry 1.1 MicroProfile Telemetry provides an adoption of the https://opentelemetry.io[OpenTelemetry] specification (currently for Distributed Tracing and Baggage in that context only). @@ -124,7 +124,7 @@ With a lack of standardization, the net result is the lack of data portability a The https://opentelemetry.io[OpenTelemetry] project solves these problems by providing a single, vendor-agnostic solution. * https://microprofile.io/project/eclipse/microprofile-telemetry -* https://github.com/eclipse/microprofile-telemetry/releases/tag/1.1-RC2 +* https://github.com/eclipse/microprofile-telemetry/releases/tag/1.1 [[mp-rest-client]] === MicroProfile Rest Client 3.0