[jira] [Commented] (MPIR-431) Dependency file details section: segregate Java version column into execution and test versions

[ASF GitHub Bot (Jira)]

    [ 
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727777#comment-17727777
 ] 

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-1569452467

   We could fix the error by taking the same scope than its parent dependency 
AND logging a warning. It is warranted to eventually succeed since direct 
dependencies must have a correct scope (otherwise the project's pom.xml won't 
pass the validation phase)
   
   
![imagen](https://github.com/apache/maven-project-info-reports-plugin/assets/1631042/8957e0c1-b189-4384-88de-435a13275efa)
   




> 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)