Hiho! In general I like the idea to have a generated list of config switches + description.
But @Inject @ConfigProperty is probably not the only way. One could use a ConfigValue, inject a Config instance, an @Configuration interface (those features are now just ConfigJSR, but will be backported to mp-config as soon as I find time). LieGrue, strub > Am 22.08.2018 um 08:59 schrieb Romain Manni-Bucau <[email protected]>: > > 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 | Blog | Old Blog | Github | LinkedIn | Book
