[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721875#comment-17721875
]
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-1544525489
I think I do understand the objective behind this change, though I am not
really happy with the output. I have changed the `full-pom` IT to contain a
runtime and provided dependency, now lets look at the output:
It doesn't look right, it says that 19 dependencies requrie Java 1.8 to run,
which is not correct and the same again with 1.5, but when tests are run they
do not require 1.5, they do require 1.8 because the max version is necessary. I
understand the opposite case where your code and deps need 1.8, but test deps
are on 11. I don't think that the information is properly visualized here avoid
misunderstandings.
> 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)
