Hi all!

I have two multi-module projects where the first one is a dependency of
the second one. Usually before a release of the second one also the first
one is released and the second one has to update the dependency-version
which is set via a property.

For this update I use versions-maven-plugin (v2.1) to do the update:

  mvn -DincludeProperties=mylib.version versions:update-properties

This used to work, when the released version was for example 1.0-beta-13
and the new development version was 1.0-beta-14-SNAPSHOT.

After I changed the new development version to always be 1.0-SNAPSHOT the
update via versions-maven-plugin stopped working. I get debugging output
like state from somebody else on StackOverflow:
http://stackoverflow.com/questions/25034556/how-can-i-update-a-property-in-a-maven-pom

For me this means version 1.0-beta-13/14 are found but than it says
"current winner is: null" and leaves the version unchanged.

Could this be a bug or am I doing something wrong?

- martin

Attachment: signature.asc
Description: PGP signature

Reply via email to