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.
As described, the dependency:tree goal on my my project complains that the dependency version is missing for a dependency that is already declared in the dependency management section of its parent pom. Please note the dependency in question is a new one and is just added in the management section.
It’s true that the parent pom has already included the dependency declaration in the dependency management section. But it’s not taken into account. To do so, we should execute the command to install the pom file in the local maven repo.
mvn -f <the absolute path to the parent's pom file> install -NBe aware that when maven resolves dependencies, it always looks for pom files already available in the repo. Instead, local files are not taken into account.