2

We are migrating our java 8 projects to java 11. JAVA_HOME still points to java 8 but the first project to be migrated compiles in java 11 and the unit tests run just fine.

The maven-compiler-plugin and the toolchain are defined as in this question. Maven version is 3.5.0.

When i run 

mvn verify

I get the following error: 

Failed to execute goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:
pmd (pmd) on project <yourproject>: 
  Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.11.0:
  pmd failed: An API incompatibility was encountered while executing 
  org.apache.maven.plugins:maven-pmd-plugin:3.11.0:pmd: 
    java.lang.UnsupportedClassVersionError: 
       <Yourclass> 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    //(indentation added for readability)

I understand that the classes were compiled using java 11 (as intended) and that maven runs on java 8 because that is what JAVA_HOME points to. But why does that trip up the pmd-plugin? It is supposed to check the source code, never mind the compiled classes.

Is there a way around this, short of setting JAVA_HOME to 11?

cb4
  • 6,689
  • 7
  • 45
  • 57
Ivana
  • 643
  • 10
  • 27
  • 1
    Please check to update PMD only https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html – khmarbaise Dec 14 '18 at 15:29
  • @khmarbaise You can make that the answer, after updating the pmd version the project builds! Thank you. – Ivana Dec 14 '18 at 15:40

1 Answers1

1

Actually, PMD does care about compiled classes for type resolution.

PMD is able to check variable types, method return types, and so on for usage in it's analysis. To do so, PMD uses the compiled classes and complete dependencies classpath.

You can disable this through the plugin's configuration by setting the typeResolution property to false, but be warned, several rules rely on this information, and when not available work on a best effort basis, which means you will get more false positives / negatives in the analysis.

PMD's analysis quality is significantly hampered by not using type resolution.

Johnco
  • 4,037
  • 4
  • 34
  • 43
  • Ok, but it appears the problem is an older version of pmd is used by default, setting the newest version in the pom (see khmarbaises comment) type resolution obviously succeeds. – Ivana Dec 14 '18 at 15:54
  • I guess, we just don't fail hard anymore, but type resolutions still doesn't work. Reporting a incomplete auxclasspath is still work in progress - so it fails silently and you might get more false positives / negatives. – adangel Dec 20 '18 at 15:53