Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(docs): add spring 6 info to migration guide #1734

Merged
merged 1 commit into from
Feb 18, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion content/update/minor/722-to-723/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,4 +58,8 @@ You can read more about the warnings [here](https://www.graalvm.org/jdk17/refere
If you want to ensure the best performance for JS execution, you can always configure the GraalVM Compiler with your JDK of choice, or use the GraalVM JDK.

More information on how to do this can be found in the official [GraalVM documentation](https://www.graalvm.org/jdk17/reference-manual/js/RunOnJDK/#graalvm-javascript-on-jdk-11).
{{< /note >}}
{{< /note >}}

# Spring Framework Upgrade

Starting with version `7.23`, the `camunda-engine` artifact now uses Spring Framework 6 by default, replacing Spring 5 from previous releases.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ You mentioned Spring 5 is still supported but must be explicitly overridden. Websphere Liberty and other impacted distros continue using spring 5. Do we still support it outside of WLS or WAS? If so, are there any tests for it? If not, do you think it makes sense to specify that Spring 5 is still used for WLS and WAS, but all other environments and the default artifacts only support Spring 6 now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I understand, the engine will still be "compatible" with both spring 5 and spring 6. The compatibility is still tested through the camunda-engine-spring (spring 5) and the camunda-engine-spring-6 (spring 6) modules. These are mentioned here. The change in the distros is about making spring-beans optional (these are transitively used by wls and was), the version of spring the distros use derives on what camunda-engine-spring module they use, and this hasn't changed.