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

Bootstrap an entire workspace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Neutral Neutral
    • None
    • 6.2.17
    • None

      Steps to reproduce

      1.  export an entire workspace (within JCR-Tools app)
      2.  Add the resulting XML in mgnl-bootstrap-sample
      3. This will work fine
      4. Now trigger an update, update the mgnl version or so.

      -> Exceptions galore.

      The 'fullpath' in info.magnolia.importexport.BootstrapUtil will become empty, so it will not remove preexisting nodes.

      info.magnolia.module.delta.SamplesBootstrapTask will btw always do ImportUUIDBehavior.IMPORT_UUID_COLLISION_THROW and I dont' see a way to override that.

      Btw, I think the name based code BootstrapUtil is error prone too. If e.g. I just make up a name for the XML in mgnl-bootstrap-sample, it will work fine, but will then fail only at an update. Using the name to determin what the path is what is going to be overrwritten seems pleonastic. The path is in the xml/yaml itself isn't it?

        Acceptance criteria

              Unassigned Unassigned
              mihxil Michiel Meeuwissen
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD