Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-13518

Another MigrateToV13 run, force it with system property

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • 13.4.3
    • 13.4.4
    • None
    • Flagged
    • Pulsar
    • Pulsar 240 - 14.3 Hardening, Pulsar 241 - Site Dev APIs 1

    Description

      There are projects for which the MigrateToV13 class didn't run correctly because the cluster wasn't brought down before upgrading (running deployment rather than stop/start). This has left incorrect properties like [hst:configuration] hst:lockedby and [hst:configuration] hst:lockedon (and more).

      13.4.2 should've fixed it, see REPO-2305, but hasn't in all cases.

      Forking the class is the only way out in case a production system is on 13.4.2 and still has those properties. Let's improve the class again, to have another round, and possibly have it listening to system property repo.MigrateToV13.force like in attached class MigrateToV13.java .

      Attachments

        Issue Links

          Activity

            People

              clientserviceteam Client Service Team
              jhoffman Jeroen Hoffman
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: