[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720323#comment-17720323
]
Gabriel Belingueres commented on MPIR-431:
------------------------------------------
Sometimes you want to target a specific runtime java version (let's say 1.7),
but use a test dependency that requires a higher java version (let's say 1.8).
The actual unique column with the max version is misleading because it seems
that the whole project targets 1.8, when in reality it's 1.7 the required
version to execute it. That's why I propose to add this one column for test
only dependencies.
> 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)
