Maven dependencyManagement version ignored in transitive dependencies

There is a simple thing. A dependencyManagement does not declare a dependency which is really used it’s only defining versions etc. which can be used.

If you define something like this it will not result in a change.

<properties>
    <guava.version>18.0</guava.version>
</properties>

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.google.guava</groupId>
            <artifactId>guava</artifactId>
            <version>${guava.version}</version>
        </dependency>
    </dependencies>
</dependencyManagement>

If you really like to overwrite the version which is used in you tree you need to define a real dependency:
So based on the above definition you need to add the following as well:

<dependencies>
    <dependency>
        <groupId>com.google.guava</groupId>
        <artifactId>guava</artifactId>
    </dependency>
</dependencies>

If you have added this please check afterwards via mvn dependency:tree.

Leave a Comment

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)