[jira] [Closed] (MPIR-431) Dependency file details section: segregate Java version column into execution and test versions

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPIR-431.
-------------------------------
    Fix Version/s: 3.4.4
       Resolution: Fixed

Fixed with [dbd863fed69f4e86dfddd82e239646a8cf61cf1f|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git&a=commit&h=dbd863fed69f4e86dfddd82e239646a8cf61cf1f].

> 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
>            Assignee: Michael Osipov
>            Priority: Minor
>             Fix For: 3.4.4
>
>
> 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)