[
https://jira.codehaus.org/browse/MPLUGIN-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359060#comment-359060
]
Michael Osipov commented on MPLUGIN-279:
----------------------------------------
This looks promising. How can I make use of that in MPIR and MPMD? If only the
property is set, does this still work? Doesn't this oppose the comments of
MJAVADOC-310 by Robert and Jason? Additionally, I do not like the wording "JDK
requirement". This is not a JDK requirement but a *Java* requirement. This is a
big difference. I am about to file an issue on that.
> 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)
