Menu
I actually was expecting powermock version 1.5.6 via transitive dependencies in a project, but i get only 1.4.11. What does this mean?
285
Multiple transitive dependencies can be excluded by using the <exclusion> tag for each of the dependency you want to exclude and placing all these exclusion tags inside the <exclusions> tag in pom. xml. You will need to mention the group id and artifact id of the dependency you wish to exclude in the exclusion tag.
How do you do this if the wrong dependency is a transitive dependency? By taking advantage of Maven's nearest definition logic, developers can override the version of a dependency by declaring it on the root pom. xml file. The example below shows an overridden version for checker-qual and how it was managed by Maven.
The dependency management section is a mechanism for centralizing dependency information. When you have a set of projects that inherit from a common parent, it's possible to put all information about the dependency in the common POM and have simpler references to the artifacts in the child POMs.
3.1.groupId – a unique base name of the company or group that created the project. artifactId – a unique name of the project. version – a version of the project. packaging – a packaging method (e.g. WAR/JAR/ZIP)
When resolving dependencies, Maven will prefer a version specified in the POM's section over the version resolved from dependencies and transitive dependencies.
Note that can be inherited from a parent POM.
See the Maven documentation on Dependency Mechanism for more info.
Specifically, check the part of the page that starts as below for a detailed explanation.
A second, and very important use of the dependency management section is to control the versions of artifacts used in transitive dependencies. As an example consider these projects:
135
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
