[
https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359063#comment-359063
]
Herve Boutemy commented on MPLUGIN-279:
---------------------------------------
let's explain: getting configuration from compiler plugin is quite effective
the only corner case is when there is no target parameter configuration:
default value from {{maven.compiler.target}} property is used, which is not
injected into plugin's configuration but calculated at runtime
> improve jdk requirement when m-compiler-p not explicitely configured: use
> default properties
> --------------------------------------------------------------------------------------------
>
> Key: MPLUGIN-279
> URL: https://jira.codehaus.org/browse/MPLUGIN-279
> Project: Maven Plugin Tools
> Issue Type: Improvement
> Components: Plugin Plugin
> Affects Versions: 3.3
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: 3.4
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
