-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Skipping Maven Central does not align with Maven #14057
Comments
Do you know if this behavior is documented anywhere? I'm wondering how someone can explicitly decide that they do not wish to query Maven Central ever, for example. Raising #14058 in preparation to revert the change |
I have found https://maven.apache.org/guides/introduction/introduction-to-repositories.html#using-repositories Using RepositoriesIn general, you should not need to do anything with the local repository on a regular basis, except clean it out if you are short on disk space (or erase it completely if you are willing to download everything again). For the remote repositories, they are used for both downloading and uploading (if you have the permission to do so). Downloading from a Remote RepositoryDownloading in Maven is triggered by a project declaring a dependency that is not present in the local repository (or for a SNAPSHOT, when the remote repository contains one that is newer). By default, Maven will download from the central repository. To override this, you need to specify a mirror as shown in Using Mirrors for Repositories. You can set this in your settings.xml file to globally use a certain mirror. However, it is common for a project to customise the repository in its pom.xml and that your setting will take precedence. If dependencies are not being found, check that you have not overridden the remote repository. For more information on dependencies, see Dependency Mechanism. Using Mirrors for the Central RepositoryThere are several official Central repositories geographically distributed. You can make changes to your settings.xml file to use one or more mirrors. Instructions for this can be found in the guide Using Mirrors for Repositories. |
🎉 This issue has been resolved in version 31.68.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
v31.68.0
Please select which platform you are using if self-hosting.
GitLab self-hosted
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
Describe the bug
Since the update from v31.63.2 to v31.68.0, most of my dependencies are no longer identified by Renovate. In order to confirm my suspicions that #13950 causes this, I created a simple POM, with a single explicitly declared repository and one dependency:
If I then run maven-dependency-plugin:tree against that POM and an empty cache, the output looks like this:
This proves the misconception that's the foundation of #13950. Maven does still fallback to Maven Central when there is an explicit repository declared in the POM.
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
No reproduction repository
The text was updated successfully, but these errors were encountered: