Migration compilation to Java 11

cnumr / ecoCode

Reduce the environmental footprint of your software applications with this cutting-edge sonarQube plugin

GNU General Public License v3.0

62 stars 48 forks source link

Migration compilation to Java 11 #164

Closed MP-Aubay closed 1 year ago

MP-Aubay commented 2 years ago

Java 8 is almost dead, long live Java 11 (even if Java 17 is already out).

Migrating plugins to Java 11 should be a good idea, as Sonarqube server already use Java 11 (https://docs.sonarqube.org/latest/requirements/requirements/).

(Not authorize to add label enhancement)

glalloue commented 2 years ago

@jules-delecour-dav : do you see any constraint to use java 11 ?

jules-delecour-dav commented 2 years ago

No constraint to use java 11 from my point of view, i have no idea of the amount of work that represent

glalloue commented 2 years ago

@MP-Aubay : GO to migrate to java 11+ You can take the action if you want

dedece35 commented 1 year ago

hello @MP-Aubay ,

I have just tested in local with last code in main branch with :

Sonar locally installed with docker
push one local java API results to my local Sonar

All is ok for me, you can close this issue unless someone else wants to test it also.

This PR duplicates #167 already merged.

med-S commented 1 year ago

Hello @MP-Aubay & @dedece35,

I have just retested the last merge #167 in the main branch. Sonar locally is working fine and all the rules are there (no error prompt). Tested also one local project in Sonar.

For me, we can close this issue since it's a duplicate.