Bukama commented on PR #728: URL: https://github.com/apache/maven-pmd-plugin/pull/728#issuecomment-5629644317
> So, this is really addressing a edge case here: Only when using maven4 (and you naturally run with java 17+ then) and want to analyze a java project, that uses e.g. java 8 or 11. In that case, you run into the problem with toolchains. > > The solution here makes the whole plugin a bit more fragile - and the logging also doesn't work anymore. > > Is it worth to support this edge case? > I think that there are still a lot of apps that target JDK 8, but I don't think that there are that much that will use such combination. My team builds on 17 but only compile against 8 - so no toolchain. However we get a lot of these auxClasspath warnings when building. A broken logging raises a "I dont like it" gut feeling. But as you can see by my words: Both are feelings, I don't have numbers. What about not supporting this edge case and wait until several users come up with such setup esp. as Maven 4 not out yet and we expect adoption will take some while? So I tend to not support this edge case. -- 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]
