[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721018#comment-17721018
]
Gabriel Belingueres commented on MPIR-431:
------------------------------------------
I don't know if I understand the question, but the value is computed as before:
it returns the max jdk version value found in all dependencies), except that
now the test scoped dependencies won't be considered for the "Java version"
summary column, instead it will be calculated as before (max jdk version value)
but summarized in a new column "Test java version". I think it makes the report
clearer and provide more useful information since the test scoped dependencies
provide less value for a user of a module.
> Dependency file details section: segregate Java version column into execution
> and test versions
> -----------------------------------------------------------------------------------------------
>
> Key: MPIR-431
> URL: https://issues.apache.org/jira/browse/MPIR-431
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
> Reporter: Gabriel Belingueres
> Priority: Minor
>
> In order to easily spot which is the minimum java version for execution
> versus the minimum java version for building the project, divide the "Java
> version" column into two columns:
> Java version: max version between dependencies with scopes: compile, runtime,
> provided, system.
> Test Java version: max java version between all the test scoped dependencies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
