Skip to content
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

FindBugs / SpotBugs collision #525

Open
SimonMarquis opened this issue Jun 27, 2023 · 0 comments
Open

FindBugs / SpotBugs collision #525

SimonMarquis opened this issue Jun 27, 2023 · 0 comments
Labels
acknowledged The issue has been acknowledged and being looked into. Further details will follow.

Comments

@SimonMarquis
Copy link

The core-api module depends on both FindBugs com.google.code.findbugs:jsr305:3.0.2 and SpotBugs com.google.code.findbugs:annotations:3.0.1.

compile group: 'com.google.code.findbugs', name: 'annotations', version: findbugsAnnotationVersion
compile group: 'com.google.code.findbugs', name: 'jsr305', version: findbugsJsrVersion

SpotBugs seems to be the "successor" of FindBugs. But this leads to unexpected errors.

Different versions are used 3.0.1 vs 3.0.2 which does not make sense to me.
And most importantly, since these are almost identical copies, it will create collision errors on the consumer side, for example:

Duplicate class javax.annotation.CheckForNull found in modules annotations-3.0.1 (com.google.code.findbugs:annotations:3.0.1) and jsr305-3.0.2 (com.google.code.findbugs:jsr305:3.0.2)

Is there a good reason to keep this "duplicated" dependency?

@jaeopt jaeopt added the acknowledged The issue has been acknowledged and being looked into. Further details will follow. label Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged The issue has been acknowledged and being looked into. Further details will follow.
Projects
None yet
Development

No branches or pull requests

2 participants