Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.5.5
-
None
-
CE, 5.6-SNAPSHOT, 5.5.6-SNAPSHOT; OS-X 10.11.6; Java 1.8.0_51
-
-
Empty show more show less
-
Kromeriz 122, Kromeriz 123
-
5
Description
Summary
If light-modules are added as symlinks to the magnolia.resources.dir, their module descriptors are not properly read. Defined dependencies are missing.
=> As a consequence, YAML !inherits fails when inheriting between light-modules.
(Because of this, i have created the ticket as a blocker)
To reproduce failure
(I)
Clone having-fun-with-yaml to /yours/dev/repo/having-fun-with-yaml
(II)
Set
magnolia.resources.dir=/yours/dev/lightmodules
(III)
In /yours/dev/lightmodules create these symlinks:
module-a -> ../repo/having-fun-with-yaml/light-modules/module-a/ module-b -> ../repo/having-fun-with-yaml/light-modules/module-b/
(IV)
Start magnolia; check the log after start or check the Definition app; both claim:
" (YAML dependency resolution) - Missing definition dependency
Problem details: Inherited definition at (module-a:components/a-component) either does not exist or is not loaded because of the missing module dependency in module (module-b), which currently depends only on () 2"
To verify that having-fun-with-yaml is ok:
(I)
see above:
(II) Set
magnolia.resources.dir=/yours/dev/repo/having-fun-with-yaml/light-modules
(III) Start the instance, this time it will work.
Checklists
Attachments
Issue Links
- relates to
-
MAGNOLIA-7196 Support read module descriptors from JCR also
-
- Closed
-
- mentioned in
-
Page Loading...