[MPLUGIN-279] improve jdk requirement when m-compiler-p not explicitely configured: use default properties

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3
• Fix Version/s: 3.4
• Component/s: Plugin Plugin
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 09/Nov/14 15:36
• Updated: 06/Apr/15 00:45
• Resolved: 09/Nov/14 17:49

Description

When m-compiler-p has no explicit configuration, plugin-info report displays "Default target for maven-compiler-plugin version xxx"

This message is misleading, since default target can be set with ${maven.compiler.target} property

The detection algorithm should look for this property

Issue Links

• is related 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