[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721978#comment-17721978
]
ASF GitHub Bot commented on MPIR-431:
-------------------------------------
belingueres commented on PR #47:
URL:
https://github.com/apache/maven-project-info-reports-plugin/pull/47#issuecomment-1545008672
Yes this is the kind of conclusions I'd like to derive about the jdk
versions by looking at the report, and just separating test scoped deps into
its own column I agree it is too simplistic, but I think it offers more value
than having only one column for all scopes.
> 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
>
> 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)
