SonarQube 10.5 compatibility

[dkeitzel]

As far as I know this should be enough to produce a binary compatible plugin for SonarQube 10.5. See also #900 (comment).

[mc1arke]

This change isn't actually required: we only need the Sonarqube build dependency to allow us to compile the plugin. Given 10.5 hasn't changed any of the APIs we use then there's nothing that we need to change; I just need to push docker images and update the README

[dkeitzel]

Are you sure? I'm by no means an expert in Java binary compatibility 😅. But at least the return type of ProjectAlmSettingDao#insertOrUpdate changed.

[mc1arke]

Are you sure? I'm by no means an expert in Java binary compatibility 😅. But at least the return type of ProjectAlmSettingDao#insertOrUpdate changed.

Sorry, I'd missed that change, and yes it will cause problems for anyone creating a new ALM setting. This means we'll need to create a release purely for 10.5 😞

[tburschka]

Any news on this?

[zisuu]

would be nice to get this solved soon. We're currently having people that can't change some settings in their Projects due to this. Thanks a lot for your efforts 👍

[gjabouley-invn]

Hello
as usual for people in a hurry, SNAPSHOT version built from this PR can be downloaded using GitHub checks artefacts: https://github.com/mc1arke/sonarqube-community-branch-plugin/actions/runs/8969366962/artifacts/1476415257

[gjabouley-invn]

Are you sure? I'm by no means an expert in Java binary compatibility 😅. But at least the return type of ProjectAlmSettingDao#insertOrUpdate changed.

Sorry, I'd missed that change, and yes it will cause problems for anyone creating a new ALM setting. This means we'll need to create a release purely for 10.5 😞

You will probably need to build a new version for each new version of SQ, why not aligning the plugin version number with SQ version ? ;)