-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage Guava without findbugs and listenablefuture, make sure they do #23686
Conversation
not soak through quarkus-maven-plugin and quarkus-bootstrap See https://issues.redhat.com/browse/QUARKUS-1742 for more details.
Please backport to 2.7 |
This workflow status is outdated as a new workflow run has been triggered. |
<bannedDependencies> | ||
<excludes> | ||
<!-- findbugs is not required at runtime --> | ||
<exclude>com.google.code.findbugs:jsr305</exclude> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This dependency is managed in the quarkus-bom. It's a runtime dependency of quarkus-grpc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine for grpc and I do not think it contradicts banning it here in quarkus-core-deployment. I mean it would be nice if findbugs does not soak to every single deployment module that depends on quarkus-core-deployment. Most, if not all deployment modules depend on quarkus-core-deployment.
If some deployment module needs findbugs, it is free to depend on it direcly. Those cases are rather rare, though.
not soak through quarkus-maven-plugin and quarkus-bootstrap
See https://issues.redhat.com/browse/QUARKUS-1742 for more details.