Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java is too old in Sonar - need to update from 11 to 17+ #251

Closed
leonardocarreras opened this issue Oct 11, 2023 · 1 comment · Fixed by #265
Closed

Java is too old in Sonar - need to update from 11 to 17+ #251

leonardocarreras opened this issue Oct 11, 2023 · 1 comment · Fixed by #265
Assignees
Labels

Comments

@leonardocarreras
Copy link
Collaborator

In the analysis, we see this message

warning The version of Java (11.0.14.1) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

@leonardocarreras leonardocarreras changed the title Java is too old in Sonar - need to update from 11 to 17 Java is too old in Sonar - need to update from 11 to 17+ Oct 17, 2023
@leonardocarreras leonardocarreras self-assigned this Nov 12, 2023
@leonardocarreras
Copy link
Collaborator Author

leonardocarreras commented Jan 24, 2024

This PR #265 does the following updates:

  • Sonar Scanner: now in version 5.0.1.3006
  • Java: using the JRE (Java 17) included with sonar (next time we only update the version of sonar)
  • Node.js: updated to version 20

dinkelbachjan added a commit that referenced this issue Jan 25, 2024
Due to end of support of the Java 11 (LTS) in Sonar, this PR updates the
version of Sonar Scanner to 5.0.1.3006. Additionally, the warnings
because of Node.js (version 16 to be unsupported in the near future) are
corrected. Actions `cache` is also updated to `v4`. The action for
`setup-java` was removed (we use now the JRE included in
`sonar-scanner`).

This closes #251
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant