adangel commented on PR #728: URL: https://github.com/apache/maven-pmd-plugin/pull/728#issuecomment-5684675642
> My team builds on 17 but only compile against 8 - so no toolchain. However we get a lot of these auxClasspath warnings when building. The auxClasspath warnings are addressed by #726 - but only if you have a matching toolchain in your toolchain.xml. You don't need to configure the toolchain-plugin, as otherwise, you'd run into exactly this issue (when using maven4). > 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. Yes, let's skip this edge case for now until there is a real need. If this happens, one solution could be, to call PMD with its own CLI classes and infra/full dependencies (currently m-pmd-p just uses a custom wrapper around PMD classes). Then PMD would use its own logging and m-pmd-p would need to tunnel the process stdout/stderr back. PMD would still write the pmd.xml file, which can be read by m-pmd-p. Will be a bit tricky to get the dependencies correct, but that could work. I'm closing this PR then. -- 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]
