Add Java 21 Support to Side projects

[psavidis]

Acceptance Criteria (Required on creation)

Java 21 is available as a build environment and by the following repositories:

• camunda-spin
• camunda-connect
• camunda-commons
• camunda-template-engines-jsr223
• feel-scala

Note: camunda-bpm-rpa-bridge-ee will be considered out of scope for the 7.21 release.

Hints

• The respective Jenkins stages (declaration and use) need to be added in .ci.cambpm file

Links

• Parent Issue
• Infra Issue for making Java 21 available to be consumed by Jenkins builds.

Breakdown

Upstream and Other Projects PR

Beta Give feedback

1. chore(project): Add JDK 21 Build Support camunda-spin#215
   +0
   
2. chore(project): Add JDK 21 Build Support camunda-connect#87
   +0
   
3. chore(project): Add JDK 21 Build Support camunda-commons#39
   +0
   
4. chore(project): Add JDK 21 Build Support camunda-template-engines-jsr223#36
   +0
   
5. chore(workflows): Add Java 21 to build-maven.yml feel-scala#803
   +0
   
6. chore(workflows): Add Java 21 to build-maven.yml feel-scala#808
   +0
   

[yanavasileva]

@psavidis, please note that Status must be Review when requesting a review.

[yanavasileva]

@psavidis, feel scala change must be backported to the minor version branch that currently is used by Camunda 7.21, which is 1.16.
Reference: https://github.com/camunda/camunda-bpm-platform/blob/master/pom.xml#L35
Hint: feel scala repo uses the backport action.

[psavidis]

@psavidis, feel scala change must be backported to the minor version branch that currently is used by Camunda 7.21, which is 1.16. Reference: https://github.com/camunda/camunda-bpm-platform/blob/master/pom.xml#L35 Hint: feel scala repo uses the backport action.

Thanks for the reminder Yana. Following a discussion with Tassilo, it makes sense to backport JDK 21 config to the 1.7 branch as a newer release and update the repo to point to the latest patch version (that would be 1.17.5).

[tasso94]

Related to bumping the FEEL Engine 1.17.5: #4075