This PR removes the Jakarta EE 10.0.0 core API dependency in exchange to use the explicit Jakarta EE dependencies needed for MicroProfile Metrics (TCK/API).
In general, MP Metrics relies on CDI and Restful WS.
Exclusions were used in the MP Metrics pom.xmls similar to that of the Jakarta EE 10.0.0 core API ( i.e. jakarta.jakartaee-core-api)at https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-core-api/10.0.0/jakarta.jakartaee-core-api-10.0.0.pom where all dependencies are excluded and only the dependencies that are needed by MP Metrics is is defined in the pom.xml (i.e. jakarta.interceptor-api and jakarta.inject-api ). This creates the lightest foot print for MP Metrics.
A proposal was provided before to import the pom.xml of the jakarta.jakartaee-core-apipom.xml. This would not work as the dependencies defined in the jakarta.jakartaee-core-apipom.xml were not within a dependencyManagement element.
Related to : https://github.com/eclipse/microprofile-metrics/issues/752
This PR removes the Jakarta EE 10.0.0 core API dependency in exchange to use the explicit Jakarta EE dependencies needed for MicroProfile Metrics (TCK/API).
In general, MP Metrics relies on
CDI
andRestful WS
.Exclusions were used in the MP Metrics
pom.xml
s similar to that of the Jakarta EE 10.0.0 core API ( i.e.jakarta.jakartaee-core-api
)at https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-core-api/10.0.0/jakarta.jakartaee-core-api-10.0.0.pom where all dependencies are excluded and only the dependencies that are needed by MP Metrics is is defined in thepom.xml
(i.e.jakarta.interceptor-api
andjakarta.inject-api
). This creates the lightest foot print for MP Metrics.A proposal was provided before to import the
pom.xml
of thejakarta.jakartaee-core-api
pom.xml
. This would not work as the dependencies defined in thejakarta.jakartaee-core-api
pom.xml
were not within adependencyManagement
element.