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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on MPIR-431:
-------------------------------------

belingueres opened a new pull request, #47:
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/47

   column into execution and test versions
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPIR) filed 
          for the change (usually before you start working on it).  Trivial changes like typos do not 
          require a JIRA issue.  Your pull request should address just this issue, without 
          pulling in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[MPIR-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MPIR-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of the 
          commit message.
    - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will 
          be performed on your pull request automatically.
    - [x] You have run the integration tests successfully (`mvn -Prun-its clean verify`).
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   




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