[jira] (MPIR-263) JDK Rev not correctly determined if compile source is an interpolated property
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-263:
Fix Version/s: 2.8
JDK Rev not correctly determined if compile source is an interpolated property
--
Key: MPIR-263
URL: https://jira.codehaus.org/browse/MPIR-263
Project: Maven Project Info Reports Plugin
Issue Type: Bug
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.source}} in the {{properties}} section or
per command line, that value is not taken into account in report generation.
The source and target version is retrieved from the static model.
I have filed a similar issue with the JavaDoc Pluing MJAVADOC-310.
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)
[jira] (MPIR-263) JDK Rev not correctly determined if compile source is an interpolated property
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MPIR-263:
Description:
If you define {{maven.compiler.source}} in the {{properties}} section or per
command line, that value is not taken into account in report generation. The
source and target version is 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.
was:
If you define {{maven.compiler.source}} in the {{properties}} section or per
command line, that value is not taken into account in report generation. The
source and target version is retrieved from the static model.
I have filed a similar issue with the JavaDoc Pluing MJAVADOC-310.
If someone could use an interpolated model that would solve the issue. At least
this should be in the FAQ list.
JDK Rev not correctly determined if compile source is an interpolated property
--
Key: MPIR-263
URL: https://jira.codehaus.org/browse/MPIR-263
Project: Maven Project Info Reports Plugin
Issue Type: Bug
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.source}} in the {{properties}} section or
per command line, that value is not taken into account in report generation.
The source and target version is 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)
[jira] (MPIR-263) JDK Rev not correctly determined if compile source is an interpolated property
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MPIR-263:
---
Assignee: Michael Osipov
JDK Rev not correctly determined if compile source is an interpolated property
--
Key: MPIR-263
URL: https://jira.codehaus.org/browse/MPIR-263
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: summary
Affects Versions: 2.6
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
Assignee: Michael Osipov
If you define {{maven.compiler.source}} in the {{properties}} section or
per command line, that value is not taken into account in report generation.
The source and target version is retrieved from the static model.
I have filed a similar issue with the JavaDoc Pluing MJAVADOC-310.
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)
[jira] (MPIR-263) JDK Rev not correctly determined if compile source is an interpolated property
[
https://jira.codehaus.org/browse/MPIR-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=355386#comment-355386
]
Michael Osipov commented on MPIR-263:
-
If no one is opposed, I would use {{maven.compiler.target}} instead of querying
the compiler plugin because this does not always work due to the statically
generated Maven model. Target cannot be reliably read from compiler plugin.
JDK Rev not correctly determined if compile source is an interpolated property
--
Key: MPIR-263
URL: https://jira.codehaus.org/browse/MPIR-263
Project: Maven Project Info Reports Plugin
Issue Type: Bug
Components: summary
Affects Versions: 2.6
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
If you define {{maven.compiler.source}} in the {{properties}} section or
per command line, that value is not taken into account in report generation.
The source and target version is retrieved from the static model.
I have filed a similar issue with the JavaDoc Pluing MJAVADOC-310.
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)
[jira] (MPIR-263) JDK Rev not correctly determined if compile source is an interpolated property
Michael Osipov created MPIR-263:
---
Summary: JDK Rev not correctly determined if compile source is an
interpolated property
Key: MPIR-263
URL: https://jira.codehaus.org/browse/MPIR-263
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Bug
Components: summary
Affects Versions: 2.6
Environment: Maven 2.2.1 and 3.0.3
Reporter: Michael Osipov
If you define {{maven.compiler.source}} in the {{properties}} section or per
command line, that value is not taken into account in report generation. The
source and target version is retrieved from the static model.
I have filed a similar issue with the JavaDoc Pluing MJAVADOC-310.
If someone could use an interpolated model that would solve the issue. At least
this should be in the FAQ list.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
