Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
as discussed in the mailing list (see my post from april 2016) i want to contribute the wcm.io Configuration parts that are not AEM-specific.
the current features of wcm.io Configuration are described here: http://wcm.io/config/
the main goal is to support "context-specific" configuration, that means configuration that is different for different content paths (e.g. sites, tenants).
during the contribution some changes and refactorings are required/planned, e.g.:
- remove some dependencies to wcm.io build environment, Guava and others
- remove the "application" distinction currently part of wcm.io Configuration in favor or a more path-based distinction
- refactor the user-faced configuration API to further simplify it and support OSGi R6-style annotation classed for typed configuration access
Update: as discussed at http://sling.markmail.org/thread/ka3ewlswfgjy7rpu the name of this new module is Context-Aware Configuration