Update migration/upgrade doc to use classpath instead of -jar for optimize migration

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Unresolved
    • Priority: L3 - Default
    • 2.3.0
    • Affects Version/s: 2.3.0
    • Component/s: None
    • None

      Current documentation uses java -jar upgrade-optimize-from-2.X.0-to-2.Y.0.jar however this triggered a bug in migration 2.2 => 2.3 when internal classpath modification (done from ctor of UpgradeExecutionPlan) wasn't triggered yet but configuration loaded as done in method UpgradeFrom22To23#buildSingleReportIdToVisualizationMap.

      Switch to more reliable manual classpath setting instead
      `java -cp ../environment:upgrade-optimize-from-2.X.0-to-2.Y.0.jar org.camunda.optimize.upgrade.main.UpgradeMain`

      In Future we will provide scripts for that, see OPT-1850.

            Assignee:
            Johannes
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: