[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17720300#comment-17720300 ] 

Michael Osipov edited comment on MPIR-431 at 5/7/23 12:27 PM:
--------------------------------------------------------------

I don't understand the explanation. Building does not necessarily require testing, you can disable it.
From a dep perspective the build version does not matter, no? The target runtime version is important.


was (Author: michael-o):
I don't understand the explanation. Building does not necessarily require testing, you can disable it.
From a dep perspective the build version does not matter, no? The Target runtime version is important.

> 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)