Given a local Maven repository, can one determine the remote repository that is the source of a particular dependency? How?
Given a local Maven repository, can one determine the remote repository that is the
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Given a local Maven repository, can one determine the remote repository that is the source of a particular dependency? How?
As mentioned by @Eugene, the origin of a dependency isn’t stored anywhere so the only way to find this after the fact (if you’re not behind a corporate repository) would be to purge the dependencies of a given project and to re-resolve them. The following goal of the Maven Dependency Plugin can do that:
Note that
reResolveis set totrueby default, I just mentioned it for documentation purposes.