-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
5.4 Sprint 1
This story is meant as preparation for the merge of configuration origins and resources and to deliver the full experience of cascade loading for the alpha version.
Criterias
- So the configuration source should be refactored in a way that it should be able to load the yaml file from resources in the future.
- There should be three different origins the yaml file can be provided: JCR, Filesystem or Classpath but can be accessed in the config source over a common file loader.
- The order for the lookup should be
- JCR
- Filesystem
- Classpath
- The file loader has the functionality to observe for changes in the origins.
- is causing
-
MAGNOLIA-6255 Resource loader fails at startup when resources module not installed
- Closed
- is related to
-
MAGNOLIA-6214 FreeMarker template scripts should be loaded with new Resource API
- Closed
- is superseded by
-
MAGNOLIA-6128 Introduce uniform resource loading API
- Closed
- relates to
-
MAGNOLIA-6266 Rename Origin and ResourcePath interfaces and impls to ResourceOrigin and Resource, respectively
- Closed
- supersedes
-
MAGNOLIA-6103 Allow for loading configuration files from resources workspace.
- Closed
- mentioned in
-
Page Loading...