Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-1926

New bootstrap mechanism: bootstrap modules files automatically if optional dependency is installed

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5 RC2
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None

      Description

      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.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                vivi Vivian Steller
                Reporter:
                vivi Vivian Steller
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                    Checklists

                    DoD