Dependency versions updated even with limited scope and processDependencies=false

[misterstrickland]

I am using the versions plugin passing these parameters:

mvn -f pom.xml org.codehaus.mojo:versions-maven-plugin:2.5:set --quiet -DgenerateBackupPoms=false -DnewVersion=18.4.0-20180724110658-SNAPSHOT -DprocessDependencies=false -DartifactId=FooBarWebServices -DgroupId=foo.bar

My POM contains the following lines:

<groupId>foo.bar</groupId>
<artifactId>FooBarWebServices</artifactId>
<version>18.4.0-SNAPSHOT</version>
<packaging>war</packaging>
<name>FooBarWebServices</name>
<description></description>
...
<dependencies>
<dependency>
	<groupId>foo.bar</groupId>
	<artifactId>BarBamV2</artifactId>
	<version>${project.version}</version>
	<type>jar</type>
</dependency>
</dependencies>

The new version passed to the plugin is determined based on ${project.version} in the POM. The dependencies are of the same version but without a timestamp. This means with 18.4.0-SNAPSHOT as the project.version property, I want to generate a new build timestamp (that is working, as you can see above), but keep the dependency versions as 18.4.0-SNAPSHOT.

I was hoping that by limiting the scope with -DartifactId=FooBarWebServices -DgroupId=foo.bar, my dependencies would not have their versions updated by the plug-in and would not be searched for by Maven. However, my build is failing looking for dependency BarBamV2-18.4.0-20180724110658-SNAPSHOT, which obviously doesn't exist.

[github-actions]

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.