• Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.6.0
    • None
    • documentation
    • None

      • given:
        • I go to the Optimize documentation of version 2.4 or 2.5
      • when:
        • I go to the plugin section, e.g. here
      • then:
        • the version tag of the optimize dependency is cutoff, like <version>.0</version>
      • expected:
        • the actual version that is currently selected is shown in the version field

      Hints:

      • the version alias is used to extract the version from the current docs
      • When you push to the branch, then the changes are only applied to the stage version. To apply the changes to the live version, you need to trigger the respective jenkins job

        This is the controller panel for Smart Panels app

            [OPT-2651] Broken maven version in docs

            Pushed directly to the branches for 2.4 and 2.5 - the ones before that didn't have the plugin page as far as I could see.

            Helene Waechtler added a comment - Pushed directly to the branches for 2.4 and 2.5 - the ones before that didn't have the plugin page as far as I could see.

            Johannes added a comment -

            Small changes that can save the world....or at least make the life for our customers easier! Well done - nothing to complain about

            Johannes added a comment - Small changes that can save the world....or at least make the life for our customers easier! Well done - nothing to complain about

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: