[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359054#comment-359054
]
Herve Boutemy edited comment on MPIR-263 at 12/14/14 8:25 AM:
--------------------------------------------------------------
I'm not convinced: I think this should be detected the same way it is done in
Maven Plugin Tools, for JDK prerequisite: see MPLUGIN-279
I'll see how to merge algorithms and write good tests, because what we are
missing is good tests to check every conditions (I'm quite sure MPLUGIN-279 is
not good at the moment in some conditions)
was (Author: hboutemy):
I'm not convinced: I think this should be detected the same way it is done in
Maven Plugin Tools, for JDK prerequisite: see MPLUGIN-279
I'll see how to merge algorithms
> Add parameter 'targetJavaVersion' and inject ${maven.compiler.target}
> ---------------------------------------------------------------------
>
> Key: MPIR-263
> URL: https://jira.codehaus.org/browse/MPIR-263
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: summary
> Affects Versions: 2.6
> Environment: Maven 2.2.1 and 3.0.3
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Fix For: 2.8
>
>
> If you define {{maven.compiler.target}} in the {{<properties>}} section or
> per command line, that value is not taken into account in report generation.
> The source and target version are retrieved from the static model.
> If someone could use an interpolated model that would solve the issue. At
> least this should be in the FAQ list.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
