[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359150#comment-359150
]
Michael Osipov commented on MPIR-263:
-------------------------------------
I'd like to clarify this first with Robert. In my opinion you misunderstood the
statement in MJAVADOC-310. The upshot is that plugins should not know of each
other. We do not have a shared config space:
bq. In one of the Maven Hangouts we spent some time on this issue. Jason is
very clear about this: plugins should have no knowledge about each other. If
there are shared configuration-elements amongst plugins, then the pom.xml might
need to be enriched for such elements.
That is the reason why I do not want to obtain information from compiler plugin.
> 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)
