[
https://issues.jboss.org/browse/WFLY-12628?page=com.atlassian.jira.plugin...
]
Jeff Mesnil updated WFLY-12628:
-------------------------------
Description:
MP Health was upgraded to 2.1 in WFLY-12555 at the same time that smallrye-health was
upgrade to 2.0.0 in WFLY-12554
That was a mistake as smallrye-health is depending on MP Health 2.0.1.
There is no harm on staying on MP Health 2.1 as the API changes are internal to the API
and do not require any implementation from the provider:
https://github.com/eclipse/microprofile-health/compare/2.0.1...2.1
However, if we decide to keep WildFly 18 under the same MP Umbrella release (3.0) at the
moment, it might be better to downgrade to 2.0.1
was:
MP Health was upgraded to 2.1 in WFLY-12555 at the same time that smallrye-health was
upgrade to 2.0.0 in WFLY-12554
That was a mistake as smallrye-health is depending on MP Health 2.0.1.
There is no harm on staying on MP Health 2.1 as the API changes are internal to the API
and do not require any implementation from the provider.
However, if we decide to keep WildFly 18 under the same MP Umbrella release (3.0) at the
moment, it might be better to downgrade to 2.0.1
Downgrade MicroProfile Health to 2.0.1
--------------------------------------
Key: WFLY-12628
URL:
https://issues.jboss.org/browse/WFLY-12628
Project: WildFly
Issue Type: Component Upgrade
Components: MP Health
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Major
MP Health was upgraded to 2.1 in WFLY-12555 at the same time that smallrye-health was
upgrade to 2.0.0 in WFLY-12554
That was a mistake as smallrye-health is depending on MP Health 2.0.1.
There is no harm on staying on MP Health 2.1 as the API changes are internal to the API
and do not require any implementation from the provider:
https://github.com/eclipse/microprofile-health/compare/2.0.1...2.1
However, if we decide to keep WildFly 18 under the same MP Umbrella release (3.0) at the
moment, it might be better to downgrade to 2.0.1
--
This message was sent by Atlassian Jira
(v7.13.8#713008)