-
Notifications
You must be signed in to change notification settings - Fork 737
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
Remove <repositories> from POMs #1809
Comments
Yes,i'm come from china . |
That helps understand how to possibly reproduce the issue, thanks. BTW, if you have an internal repository, then you probably should setup a mirror in your Maven settings.xml with |
Fixes #1809 PiperOrigin-RevId: 350411219
Fixes google#1809 PiperOrigin-RevId: 350419816
Description of the problem / feature request:
The
error_prone_core
POM contains a<repository>
, which shouldn't be needed but will be inherited by users' builds (in Maven, not Gradle; don't know about other build tools)Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
The error was reported on the gradle-errorprone-plugin issue tracker: tbroyer/gradle-errorprone-plugin#47, I don't have more information (user seems to be Chinese, so it might be related to the Great Firewall, or it could be something entirely different), but having declared
<repositories>
in published POMs is not a good practice.What version of Error Prone are you using?
The repository is present in the 2.4.0 POM, and many previous versions: https://search.maven.org/artifact/com.google.errorprone/error_prone_core/2.4.0/jar
Have you found anything relevant by searching the web?
The repository was added 8 years ago in 2550253, apparently because
com.google.code.findbugs:jsr305:2.0.1
was not available in Central.According to https://search.maven.org/artifact/com.google.code.findbugs/jsr305, it was there already at the time though, so this repository shouldn't even have been added to begin with, but here we are.
I suggest removing those lines from the POM and confirm that the project still build correctly (even from a clean state / empty local repository).
The text was updated successfully, but these errors were encountered: