Support MP 3.2; add full and core MP bundles and deprecate existing numbered ones #1143
Conversation
…d bump mp version to 3.2
tjquinno
changed the title
| @@ -41,7 +41,7 @@ | |||
| <dependencies> | |||
| <dependency> | |||
| <groupId>io.helidon.microprofile.bundles</groupId> | |||
| <artifactId>helidon-microprofile-3.1</artifactId> | |||
| <artifactId>helidon-microprofile-core</artifactId> | |||
There was a problem hiding this comment.
This should be full microprofile as well.
There was a problem hiding this comment.
One benefit of doing what you suggest is that users can then use any of the MP technologies if they use the example pom, without having to change which bundle they reference.
The cost is the possible confusion as to why the example - which actually only requires core - declares a dependency on the full bundle.
I assume you are OK with that trade-off.
There was a problem hiding this comment.
This is a basic example that shows how to start MP. I expect people use example as a first step to use Helidon - e.g. it is expected that additional MP specs will be used.
| </description> | ||
|
|
||
| <dependencies> | ||
| <dependency> | ||
| <groupId>io.helidon.microprofile.bundles</groupId> | ||
| <artifactId>helidon-microprofile-3.1</artifactId> | ||
| <artifactId>helidon-microprofile-core</artifactId> |
There was a problem hiding this comment.
This should be full microprofile
…o io.helidon.security.integration:helidon-security-integration-jersey-client (needed to pass our MP security test and for most common use cases)
…l test, which relies on the MP bookstore app, will find the endpoints it expects
As part of support for MicroProfile 3.2 we are adding two new MP bundles:
helidon-microprofile-core(basically what's needed for the server) andhelidon-microprofile(everything).We are also deprecating (but not yet removing) the bundles numbered after the MP version numbers.
The coding changes add the new bundles and also update all dependencies in Helidon that used to refer to the 3.1 MP bundle. The javadoc component had a dependency on the 1.2 bundle that has also been updated.
There are a few components (not included in this PR) which currently depend on some earlier (pre-3.1) MP bundle. We will need to decide for each what to do when we actually remove the numbered bundles in a future Helidon release: