[
https://issues.apache.org/jira/browse/MPIR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728016#comment-17728016
]
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-1570407832
> I'll try to work on a PR if not too complex.
>
> > > 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)
> > >
> >
> >
> > Sounds good. Do you want to work on a PR?
>
> I'll give it a try
Don't waste your time, if it takes more than one hour. Before the faulty
method is called we can test the scope for validity and log a warning that this
artifact is ignored from the global calculation. Done.
> 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)
