Jeff Mesnil

This is a valid use case to be able to inspect the actual values used by the application but I don't think this requires to be exposed by the API....

just a bump that the ConfigJSR now has some notion of project stage as mentioned in https://github.com/eclipse/ConfigJSR/blob/25edda2914155ac6b30f821f9ef13e92b7350a3a/api/src/main/java/javax/config/ConfigAccessor.java#L172. @struberg I'm not sure whether that was intentional to have it with ConfigAccessor...

I vote for `javaxconfig.properties`. It unambiguously specifies that this properties file is about `javax.config`. `application.properties`, `configuration.properties` or `config.properties` are generic, non-descriptive names that could conflict with other libraries or implementations.

My expectation for this feature would be to centralize and share some configuration between applications (e.g. different deployed microservices could load their config from the same properties file). I would...

What's the advantage compared to having a simple class that injects @ConfigProperty in its fields?

Most importantly, congrats for the baby! :) I debugged the loading and execution of the `MetricCdiInjectionExtension` extension in WildFly. The class is loaded with the EAR module class loader. When...

An improvement is to let users choose the archs of their images (in the draft, hard-coded to produce `linux/amd64,linux/arm64` images)

The downside of that approach is that users can no longer add custom Docker `RUN` instructions to the application images and they no longer have a `Dockerfile` template to copy......

I manually verified that the new distributions content is identical to the existing ones with additional metadata in `.installation`: ``` $ diff -r ~/tmp/wildfly-33.0.0.Beta1-SNAPSHOT-galleon-maven-plugin/ ~/tmp/wildfly-33.0.0.Beta1-SNAPSHOT-wildfly-maven-plugin/ Only in /Users/jmesnil/tmp/wildfly-33.0.0.Beta1-SNAPSHOT-wildfly-maven-plugin/.installation: README.txt Only...

I also updated the `docs` module to provision with the WildFly Maven plugin for consistency sake. @bstansberry I did not update the `ee-dist` distributions that we are not publishing but...