[
https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi...
]
Jeff Mesnil commented on WFLY-13779:
------------------------------------
When is the `config.source.properties.path` system property set?
With
https://github.com/wildfly/wildfly/pull/13247 changes, the config source can now be
read by other subsystems before any deployment is done.
If the sys prop was set during deployment while the config source was configured by the
subsystems, that would be an issue in the test fixture.
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)