microprofile-config | MicroProfile Configuration Feature | Configuration Management library

This is a config issue, you are using io.helidon.Config.create() which doesn't support microprofile-config.properties.

If you use Server.create().start(), microprofile-config.properties will work out-of-the-box.

If you want to pass your own instance of config, you can do it like this:

You also need to install the extensions "org.wildfly.extension.microprofile.config-smallrye" and "org.wildfly.extension.microprofile.opentracing-smallrye" before adding the subsystems. Also wildfly provides a standalone-microprofile.xml that can server as example.

You were pretty close, just follow the rules mentioned in the docu:

1. Replace each character that is neither alphanumeric nor _ with _; then convert the name to upper case (i.e. COM_ACME_SIZE)

So given we have a config property named server.environments[0].apps[0].name when you replace each non-alfanumeric character with _ and convert to upper case you end up with: SERVER_ENVIRONMENTS_0__APPS_0__NAME. Note the double underscore between 0 and APPS as you substitute both . and [ for _. That will certainly not win any prize for the prettiest env var name but it does the job :).

You can check how exactly it is done in the Smallrye implementation of MP config - which is the implementation used by Quarkus.

Indeed you have a clash in RestEasy (transitive) dependencies in your project:

If you want to set mp.config.profile from server.env, you probably need to set MP_CONFIG_PROFILE instead.

Since dots aren't valid in environment variable names, MP Config defines some mapping rules when looking up config from environment variables. It will check for the requested name with non-alphanumeric characters converted to underscores, and then again also with all letters converted to uppercase.

Could you try with a clean ~/.m2/repository/ (just move yours away before trying)?

In order to send a JMS message to remote ActiveMQ Artemis queue that is embedded in JBoss EAP you can use the default standalone-full.xml. You don't need to set up a remote connector, pooled connection factory, or remote binding. You simply need to lookup jms/RemoteConnectionFactory from your client using JBoss EAP JNDI context. To be clear, when ActiveMQ Artemis is embedded in JBoss EAP remote clients use the JBoss EAP JNDI context not the ActiveMQ Artemis JNDI context since EAP itself is in charge of all JNDI operations.

Your client is using the ActiveMQ Artemis JNDI context: