[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Belingueres updated MPIR-431:
-------------------------------------
Description:
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.
was:
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:
Execution Java version: max version between dependencies with scopes: compile,
runtime, provided, system.
Build Java version: max version between the execution Java version, and the
test scoped dependencies.
Summary: Dependency file details section: segregate Java version column
into execution and test versions (was: Dependency file details section:
segregate Java version column into Execution and Build versions)
> 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)
