[
https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi...
]
Jeff Mesnil commented on WFLY-13779:
------------------------------------
This issue appeared after WFLY-12549 because now subsystems can depend on
microprofile-config-smallrye resources for their configurations.
Before that bug fix, subsystems were not able to use them (which was not correct from a MP
point of view) and this bug was hidden.
But you would have encountered the same issue if you had:
* set a sys prop
* add a config-source that depends on this sysprop
* deploy an application that calls Config.getConfig()
* removes the sys prop
=> at that point the application would use the config-source prop that is no longer
correct and it would throw an exception similar to yours.
I'll add a test to WildFly to highlight this issue.
MicroProfile Metrics tests started to fail since changes in
ConfigSource
------------------------------------------------------------------------
Key: WFLY-13779
URL:
https://issues.redhat.com/browse/WFLY-13779
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Reporter: Sultan Zhantemirov
Assignee: Jeff Mesnil
Priority: Major
WildFly build: 21.0.0.Beta1-SNAPSHOT
Java: oracle-java-11
A several failures appeared in our small standalone test suite [1] for MicroProfile on
WF/EAP. To be more specific, a few failures in MP Metrics that have one common cause:
{noformat}
java.lang.RuntimeException: config.source.properties.path property not defined
{noformat}
caused by line [2].
I have a reason to believe that this PR [3] could be reason of these failures. What
should be done in this case?
Thank you.
[1] -
https://github.com/jboss-eap-qe/eap-microprofile-test-suite/tree/master/m...
[2] -
https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/8b726042...
[3] -
https://github.com/wildfly/wildfly/pull/13247
--
This message was sent by Atlassian Jira
(v7.13.8#713008)