bodunov

Here I post my solution to this problem. It is built using variable expansion and type conversion. ``` java @Sources({"file:config.txt"}) public interface MyConfig extends Config { @Separator(",") @Key("servers.list") @ConverterClass(ServerConverter.class) List...

ok, I think I just found an answer by browsing the latest sources.. Use Preprocessor then.

Why would you need nested configuration for this case? For your configuration you can have one interface and three keys/methods like this: ``` java @Key("db.url") String url(); ``` Perhaps, you...

The proposed solution is good when you don't know the name of some property (section). But if all properties' names are known beforehand and you just want to make a...

There is no thread which explains how to actually get rid of multiple @Sources. There is just a thread where this issue was brought up and considered to be doable:...