-
Notifications
You must be signed in to change notification settings - Fork 155
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
Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
Comments
…or sonar 9.8. * Dealt with various api changes. * Removed support for Java versions <6, added support for 19, 19-preview, 20, 20-preview. * use central maven as artifactory instead of jfrog which lost anonymous login. * Part of: Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
* Fixed: XML parsers should not be vulnerable to XXE attacks * Part of: Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
* Part of: Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
* upgrade java frontend and plugin api dependencies * Part of: Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
* Part of: Make sonar-pmd up to date with PMD 6.55, support up to java20-preview, and allow java21 #422
Release 3.5.0 is available here |
Can you please also publish this release so that it becomes available in the SonarQube Marketplace? https://community.sonarsource.com/t/deploying-to-the-marketplace/35236 |
Yes, just set things in motion at SonarQube, see: |
Hi, it seems that the new release is not compatible with Java 11. Could it be that this release is not in sync with the latest LTS version of SonarQube? I reported it now as a separate issue: #464 |
Hi Alix,
Yes, it needs Java 17.
We'll try to fix this in 3.5.1.
Op ma 6 mei 2024 om 08:41 schreef Alix ***@***.***>:
… Hi, it seems that the new release is not compatible with Java 11. Could it
be that this release is not in sync with the latest LTS version of
SonarQube?
image.1.1.png (view on web)
<https://github.com/jborgers/sonar-pmd/assets/5415786/4620d994-7942-4640-a000-67c0a4259d20>
—
Reply to this email directly, view it on GitHub
<#422 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3TVWZWA3SK6YO6NXCRKJTZA4QTHAVCNFSM6AAAAABCW7Q76KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGI4TAMJUG4>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
3.5.0 is available in the marketplace, so closing this issue |
Hi, maybe this is expected but I get the following notice when analyzing using JDK 21 (I'm not sure if this is an error, warning or other): "Requested Java version 21 ('sonar.java.source') is not supported by PMD. Using maximum supported version: 20-preview." |
Yes, it is expected. As far as I've tested, 20-preview is equal to 21. The scan does not break anymore, just warns and continues. |
PMD 6.55 is the latest and probably the last PMD 6 release.
PMD 7 is backwards incompatible with PMD 6, so custom rules from pmd 6 will not work in pmd 7.
We would like to support LTS Java 21, however this is not supported by pmd 6.
Last one supported is java20-preview. It seems to cover all or at least most of the java 21 features.
We'd like to not break Sonar on Java 21, rather warn about it and log warn when it encounters a parse exception.
The text was updated successfully, but these errors were encountered: