[1.3.z] Pinning external application branches to 3.2

[mjurc]

Summary

• Pinning usages of Camel on Quarkus and Quarkus quickstarts to 3.2 release stream branches.

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[mjurc]

run tests

[rsvoboda]

Looks good, let's wait for CI.

[rsvoboda]

What about TodoDemoIT. That should probably have some pinning too @mjurc ?

[rsvoboda]

aha, @Disabled("Disabled until Quarkus 3 is released and TODO application migrates to it")

[mjurc]

Sadly last time that app got an update was with 2.7.1.

[rsvoboda]

Run OpenShift Tests in JVM are red, @mjurc can you investigate?

[mjurc]

@rsvoboda The job needs to be ran on JDK17 executors. I will update it, as JDK11 is deprecated anyway - wdyt?

[rsvoboda]

What requires JDK 17?

[mjurc]

@rsvoboda The Apache Camel extension for Quarkus quickstart has compilation target set to JDK17. Since we run the tests on JDK 11, the application gets built locally into container image, deployed and referenced from OpenShift deployment.

Sadly, since the executor is on JDK 11, it cannot compile the quickstart:
https://github.com/apache/camel-quarkus-examples/blob/3.2.x/file-bindy-ftp/pom.xml#L41