Bump pax.exam.version from 4.13.5 to 4.14.0

[dependabot]

Bumps pax.exam.version from 4.13.5 to 4.14.0.
Updates org.ops4j.pax.exam:pax-exam-container-native from 4.13.5 to 4.14.0

Updates org.ops4j.pax.exam:pax-exam-junit4 from 4.13.5 to 4.14.0

Updates org.ops4j.pax.exam:pax-exam-cm from 4.13.5 to 4.14.0

Updates org.ops4j.pax.exam:pax-exam-link-mvn from 4.13.5 to 4.14.0

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[garydgregory]

Keep around until we bump Java versions, eventually.

 class file has wrong version 55.0, should be 52.0

[ppkarwasz]

It is curious that projects that almost reached their end-of-life, suddenly bump the JRE requirements.

Do we need to run tests using JRE 8? Can't we just use --release 8 and rely on the quality of the compiler?

[garydgregory]

We do use the release flag if you run the build with an appropriate Java version. I run all my local release candidates with Java 17 for example and rely on the GitHub CI to prove that all LTS versions are OK. When I validate a RC that doesn't do that, I run lots of different builds using different Java versions.

You must test against Java 8 because you want to know that there are no surprises at runtime. It's not enough to compile with a flag.

We need to continue to monitor Java surveys to get an idea of when we would not loose too many users by requiring a more modern Java version.

This approval doesn't make sense since the build is broken.