[
https://issues.apache.org/jira/browse/MPMD-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ed Randall updated MPMD-39:
---------------------------
Comment: was deleted
(was: maven-pmd-plugin should be
[toolchains-aware|https://maven.apache.org/guides/mini/guide-using-toolchains.html]
and pick up the correct JDK used for compilation.
If toolchains is in use, it should select that one, not use the same JDK that
maven is running.
We have an enterprise build system when maven runs under JDK 1.8. Some
projects target 1.8, others target 11. PMD cannot cope with 11 code when it's
running under 8 and when the target is 11, we are forced to set
typeResolution=false, to avoid all sorts of strange errors (eg. 'unused private
method' despite it being used 28 times in the same class).)
> Target JDK should default to configuration of the compiler plugin
> -----------------------------------------------------------------
>
> Key: MPMD-39
> URL: https://issues.apache.org/jira/browse/MPMD-39
> Project: Maven PMD Plugin
> Issue Type: Improvement
> Reporter: Eric Bernstein
> Assignee: Dennis Lundberg
> Priority: Major
>
> It seems unnecessary to configure the target jdk twice; once for the
> compiler, and once for pmd.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
