New bootstrap mechanism: bootstrap modules files automatically if optional
dependency is installed
--------------------------------------------------------------------------------------------------
Key: MAGNOLIA-1926
URL: http://jira.magnolia.info/browse/MAGNOLIA-1926
Project: Magnolia
Issue Type: Improvement
Components: core
Affects Versions: 3.5 RC2
Reporter: Vivian Steller
Assigned To: Vivian Steller
Fix For: Green
In 3.5-rc2 we already have a mechanism for bootstrapping sample files of a
module. This is realized by SamplesBootstrapTask and IsInstallSamplesTask,
which in turn checks for a property in magnolia.properties that decides if the
samples are installed or not.
It would be very helpful to generalize this bootstrap feature so that whenever
a module has
* a /mgnl-bootstrap-DEPENDENCY folder containing bootstrap files
* an appropriate DEPENDENCY optional module dependency
* and the optional DEPENCENCY is installed
these dependency specific bootstrap files will be installed.
E.g. the workflow module version handler bootstraps an activation command
depending on the existence of the DMS module. Since all bootstrapped files are
located in the same folder under /mgnl-bootstrap and only one of them needs to
be bootstrapped conditionally it is very annoying to overwrite default
bootstrap behavior of DefaultModuleVersionHandler to solve this properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
