Java 8 support broken
See original GitHub issueAfter updating to the latest release (v1.2) we’re now getting the following error when running our scans:
The plugin [aemrules] does not support Java 1.8.0_111: com/cognifide/aemrules/AemRulesSonarPlugin
has been compiled by a more recent version of the Java Runtime (class file version 55.0),
this version of the Java Runtime only recognizes class file versions up to 52.0
Was dropping Java 8 support intentional? If not, I think just setting the Maven compiler plugin’s source/target settings to 1.8 would fix it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Known Issues for JDK 8 - Oracle
This document describes known issues in the Oracle JDK 8 release. ... It has been found that some Windows GDI functions don't support...
Read more >Java 8 release changes
Java 8 Release Highlights. This article applies to: Java version(s): 8.0. This page highlights changes impacting end users for each Java release.
Read more >Upgrading Java 8 to 11 is broken - kronis.dev
Furthermore, it feels like new runtime and package versions are made in ways that accidentally break backwards compatibility with no clear ways to...
Read more >Java 8 support broken · Issue #201 - GitHub
The plugin [aemrules] does not support Java 1.8.0_111: com/cognifide/aemrules/AemRulesSonarPlugin has been compiled by a more recent version of the Java ...
Read more >Do Java 8 default methods break source compatibility?
Any new method in a superclass or interface can break compatibility. Default methods make it less likely that a change in an interface...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have the same Problem with our Company. We have some projects still on Java8 so I had to uninstall the Plugin for everyone. Would it be possible to disable the analysis via configuration or just skipping the AEM Rules part if the project is using Java8? Right now it breaks the build which is rather unfortunate.
I have the same problem. We can use java 11 for sonarqube task only. This is inconsistency though.