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)
   > > > 
![imagen](https://user-images.githubusercontent.com/1631042/242152975-8957e0c1-b189-4384-88de-435a13275efa.png)
   > > 
   > > 
   > > 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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to