In the following table the features for the next version are gathered. At some point the decision which will become part of V 2.0 will be made and the table splitted. For complicated features a separate (linked) page should be added and link to the page entered in the below table.
An object should be able to configure how errors are handled (Example: does an error in @BeforeConfiguration annotated method stops the configuration or can ConfigurationManager ignore it).
Currently JSON is the only source format we understand. Xml and properties could be added for 'old-style' developers, yaml/groovy for 'modern' people.
A RemoteConfigServer to be used instead of files
A possibility to retrieve all known configurations and all known environment