BE: Chore: Upgrade java to 21

[sixdouglas]

Resolves #490
bump java version to 21

• kafka client: 3.3.1 -> 3.8.0
• aspectj: 1.9.9.1 -> 1.9.21

Maven Plugins:

• clean: 3.2.0 -> 3.4.0
• compile: 3.10.1 -> 3.13.0
• resources: 3.2.0 -> 3.3.1
• surefire: 3.1.2 -> 3.5.1
• openapi generator : 6.6.0 -> 7.9.0
• springdoc openapi webflux: 1.2.32 -> 1.8.0
• surefire: 3.2.3 -> 3.5.1 (for e2e tests)
• surefire-ng: 3.2.5 -> 3.5.1 (for e2e tests)

• Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• No need to
• Manually (please, describe, if necessary)
• Unit checks
• Integration checks
• Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• My changes generate no new warnings (e.g. Sonar is happy)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[sixdouglas]

Hi @Haarolean,

Here is another PR to bump versions of several components, trying to go to Java 21 another step to #490.

I still haven't been able to run the smoke, regression or sanity tests on my Mac M1. I've managed to solve some issues around docker incompatibilities like kdsqldbor the create-connectors images in the documentation/compose/e2e-tests.yaml file.

[Haarolean]

Yeah I remember having issues with running e2e on m1 as well, mostly due to x86-based images in e2e compose. As an alternative, you can run them in your forked repo.

[sixdouglas]

The build is failing, it seems that it uses the version of the scripts on the main branch and not the updated ones in the PR.

[sixdouglas]

As an alternative, you can run them in your forked repo.

I didn't know I could do that, do you have a link to explain it?

[sixdouglas]

I still can't make the e2e tests work locally.
But I was able to reproduce and fix the exception raised in the smoke tests you run.

[Haarolean]

As an alternative, you can run them in your forked repo.

I didn't know I could do that, do you have a link to explain it?

sorry I don't have any articles on this, the point is that you can fork the repo and run whatever changes you need even on modified workflows in the fork repo :) There will be some failing tasks (due to lack of set secrets) like release and e2e reports uploading, but that's not that important.

[Haarolean]

I still can't make the e2e tests work locally. But I was able to reproduce and fix the exception raised in the smoke tests you run.

oh, thanks much! 😄

[Haarolean]

All workflows seem to be passing successfully on a fork

[germanosin]

Thanks for contribution!

[Haarolean]

@sixdouglas hey, would you be able to fix current conflicts? I want to merge this next so we don't have any future conflicts here. I can take it from here if you don't have an opportunity to resolve the conflicts atm.

[sixdouglas]

Hello @Haarolean
Rebase should be ok. Local build is so 🤞🏻

[Haarolean]

@sixdouglas thank you for your contribution!

[sixdouglas]

Thank you for accepting my contribution