Describe the bug
Found an issue where having packages/classes in a dependency's module.xml with Deploy="true" does not work. After install, those resources are still readable and writable. The base module does correctly have deployed code for resources that specify it.
To Reproduce
Steps to reproduce the behavior:
- Have a module with a resource marked with
Deploy="true" that is a dependency of another module
- Install the base module which includes this dependency
- Package the base module, make sure to include the
-export-deps 1 flag to include the dependency
- Load module from the packaged tarball
Expected behavior
The resources installed marked with deploy should be deployed on load from the packaged tarball.
Describe the bug
Found an issue where having packages/classes in a dependency's module.xml with
Deploy="true"does not work. After install, those resources are still readable and writable. The base module does correctly have deployed code for resources that specify it.To Reproduce
Steps to reproduce the behavior:
Deploy="true"that is a dependency of another module-export-deps 1flag to include the dependencyExpected behavior
The resources installed marked with deploy should be deployed on load from the packaged tarball.