Lilian BENOIT

I agree with @jmesnil , It is interesting for debug goal > We can however mention in the spec that the implementation SHOULD provide some ways to inspect and list...

I agree with @sdaschner , a ProjectStage promote internally configuration. But developers use this system. if that can permit that they don't build artifact per environment So a +1 from...

As deltaspike, have we a list of stage ? or name is completely free ? it's perhaps the different between stage and profile I prefer multi-file for stage or profile.

But file **javaconfig-${stage or profile}.properties** overload properties of file **javaconfig.properties** We can have only specific properties by this profile or stage wdyt ?

I prefer using META-INF. Here is a extract from guide jar : > The following files/directories in the META-INF directory are recognized and interpreted by the Java 2 Platform to...

Sorry @sdaschner @Emily-Jiang , but name change is not sufficient. Spring loads property file in root folder ([doc](https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html)) Personnaly, i prefer META-INF location. It's common on Java EE config file....

APP-INF is bad because that's do reference at **EAR**. Several container don't support this type of module. (ex: tomcat) META-INF is more neutral. It's valid for classic JAR (_META-INF_), **WAR**...

+1 I think a good way for externalized configuration On Linux, we are already locations as `/etc/java` et `~/.java` We could have `/etc/java/config` et `~/.java/config`

+1