[MPMD-170] Have targetJdk default to maven.compiler.target

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.1
• Fix Version/s: 3.4
• Component/s: PMD
• Flags: Patch
• Assignee: Michael Osipov
• Reporter: Stevo Slavić
• Created: 29/Jun/13 14:56
• Updated: 11/Nov/17 17:27
• Resolved: 26/Nov/14 09:33

Description

Currently targetJdk has to be defined separately from maven.compiler.target property that most plugins already default to, so target JDK information is unnecessarily repeated, making POMs with maven-pmd-plugin less DRY, harder to maintain, prone to mistakes and unwanted behavior.

So, please make targetJdk default to maven.compiler.target property.

Attached is MPMD-170.patch which adds this behavior.

Issue Links

• is duplicated by: MPMD-194 Set ${maven.compiler.target} as the default value for targetJdk parameter
• relates to: MPMD-245 targetJdk property should use maven.compiler.source by default
• relates to: MJAVADOC-310 compiler plugin settings aren't inherited from parent for linking Java API links
• relates to: MPIR-263 improve minimum java requirement when m-compiler-p not explicitely configured: use default properties