You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
jaeopt
added
the
acknowledged
The issue has been acknowledged and being looked into. Further details will follow.
label
Jun 27, 2023
The core-api module depends on both FindBugs
com.google.code.findbugs:jsr305:3.0.2
and SpotBugscom.google.code.findbugs:annotations:3.0.1
.java-sdk/core-api/build.gradle
Lines 5 to 6 in c507649
SpotBugs seems to be the "successor" of FindBugs. But this leads to unexpected errors.
Different versions are used
3.0.1
vs3.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:
Is there a good reason to keep this "duplicated" dependency?
The text was updated successfully, but these errors were encountered: