Hi guys, What about adding in the project a mojo to scan @ConfigProperty usages (potentially we can scan for getOptionalValue/getValue usages too but not sure we should do it upfront) and dump them in an adoc (we can make it pluggable later if requested). Goal is to have some auto doc for the config very quickly and without effort.
My main question is how to get the documentation part of each config entry. In my apps I tend to add a @Documentation annotation which is usable at build and runtime times but wonder if if there is a way to avoid it without using the javadoc parsing which would be my last option. Are you for this feature? Any idea for the doc issue? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance>
