Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-7160

Update documentation for Spring boot 3 migration

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • L3 - Default
    • 3.11.0-alpha5, 3.11.0
    • None
    • None
    • None
    • Not defined

    Description

      With the migration to Spring Boot 3 a lot has changed in the code base. Some of them are breaking changes that need to be properly documented and communicated to the customers. Here are they:

      • All documentation updates need to be done for both 3.10 and 3.11
        • But slightly differently. For 3.10, we need to be explicit that only the patched version onwards has the changes applied
      • We now use Java 17 instead of 11, also update https://docs.camunda.io/docs/reference/supported-environments/
      • With the change to the jakarta libraries, customer plugins will no longer work and will need to be updated to work with Java 17 (javax->jakarta changes)
      • Document the steps needed to rebuild the plugins with new jakarta dependencies
      • There were some changes made to the logback configuration. Customer will need to adjust logging files. Customers that were using custom configurations will need to refactor them. They can use the new environment-logback.xml as template 
      • Document the changing behaviour with trailing slash behaviour
      • Update the plugin examples?

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                giuliano.rodrigues-lima Giuliano Rodrigues Lima
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce