I'm encountering an issue after upgrading the Maven Versions Plugin.
We execute the versions:use-dep-version goal from our root POM in a multi-module project using the following command:
mvn versions:use-dep-version \
-DdepVersion="[2025.19.0,2025.19.99999]" \
-DforceVersion=true \
-DexcludeReactor=false \
-Dincludes="com.mycompany*:*" \
-B \
-pl module1,module2,module3
Behavior Change After Upgrade
Plugin Version 2.14.2: This command succeeds for all specified modules (module1, module2, and module3).
Plugin Version 2.15.0 and Later: Only module1 succeeds (returns SUCCESS). The remaining modules, module2 and module3, are skipped (return SKIPPED).
I have attempted to run with the -X (debug) flag but have been unable to identify the reason for the skipping behavior in the latter modules following the upgrade.
I'm encountering an issue after upgrading the Maven Versions Plugin.
We execute the
versions:use-dep-versiongoal from our root POM in a multi-module project using the following command:Behavior Change After Upgrade
Plugin Version 2.14.2: This command succeeds for all specified modules (module1, module2, and module3).
Plugin Version 2.15.0 and Later: Only module1 succeeds (returns SUCCESS). The remaining modules, module2 and module3, are skipped (return SKIPPED).
I have attempted to run with the -X (debug) flag but have been unable to identify the reason for the skipping behavior in the latter modules following the upgrade.