[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728030#comment-17728030
]
ASF GitHub Bot commented on MPIR-431:
-------------------------------------
michael-o commented on PR #47:
URL:
https://github.com/apache/maven-project-info-reports-plugin/pull/47#issuecomment-1570453498
@belingueres This is my proposal:
https://github.com/apache/maven-project-info-reports-plugin/commit/a38c46bd149aa0cae39a5abdb5d34106275cb3db
No fuzz, straight forward.
> 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)
