ascopes commented on issue #944: URL: https://github.com/apache/maven-plugin-tools/issues/944#issuecomment-3654163055
@slawekjaranowski hey... apologies for the ping, and appreciate you are all super busy with Maven 4 preparation. Until we see a release of the qdox fixes by @paul-hammant to Maven Central, would it be possible to request some mitigations of this issue on the maven-plugin-plugin side? Asking since I've unfortunately been blocked from merging changes on my project since July, since I cannot get a successful Maven build while this issue is outstanding, and the problematic code is generated for me using a third party library that I do not have control of. It would appear that either being able to explicitly exclude classes from being scanned by QDox, being able to stop generated-sources from being scanned, or being able to treat parsing errors as a warning would allow me to get past this issue, but I don't know enough about how this is used under the hood to know if that is possible or not. -- 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]
