[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359173#comment-359173
]
Robert Scholte commented on MPIR-263:
-------------------------------------
[Here's|https://www.youtube.com/watch?v=EA5JntR759s&feature=player_embedded#t=675]
the hangout I was referring to. Right now we don't have a good solution, both
the $\{maven.compiler.target} and the reading of the compiler-plugin
configuration are workarounds for something we cannot fix right now. the
parameter is probably the cleanest solution, but requires the user to specify
this as a property in his pom.xml. Reading the configuration is more user
friendly, but clashes with the concept that plugins shouldn't be aware of each
other.
> 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)
