Lets say I have a multi-module project
Project A (pom.xml)
- B (module pom.xml)
- C (module pom.xml)
Now in A's pom.xml, under dependency management, i have the following dependency:
<dependency>
<groupId>com.mycompany</groupId>
<artifactId>C</artifactId>
<version>1.0.0-SNAPSHOT</version>
<dependency>
In B's pom.xml I use the above dependency.
<dependency>
<groupId>com.mycompany</groupId>
<artifactId>C</artifactId>
<dependency>
Now lets say I run the following command on the root pom.xml (A's pom.xml)
mvn versions:set -DnewVersion=137.0.18 -DprocessDependencies=false
This command only sets the version for the parent and the submodules version (but doesn't update the dependency), which is as expected.
Now if I want to run the following command and process the dependency as well, like this:
mvn versions:set -DnewVersion=137.0.19 -DprocessDependencies=true
Now it does NOT process the dependency. Had if I ran the first command with processDependencies=true, it would have updated the dependency. I am unable to understand why running it the second time its not processing the dependencies? Sounds to me like a bug on versions plugin.