[mojo-dev] [jira] (MVERSIONS-187) Changing properties (e.g. versions:update-property) doesn't work if the property it referenced at ad dependencyMangement Section

[Ilko Iliev (JIRA)]

Title: Message Title

Ilko Iliev commented on an issue   Re: Changing properties (e.g. versions:update-property) doesn't work if the property it referenced at ad dependencyMangement Section I'm experiencing the same issue and it is not clear to me, if this is supposed to work or it is a bug - simply put, what is the behaviour of the allowSnapshots=false, if the latest SNAPSHOT version is referenced in the pom and versions:update-properties goal is run? My debug output shows me now: [DEBUG] Property $ {uirdomainconstants.version}: Set of valid available versions is [1.3.0, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4] [DEBUG] Property ${uirdomainconstants.version} : Restricting results to null [DEBUG] Property $ {uirdomainconstants.version}: Current winner is: null [DEBUG] Property ${uirdomainconstants.version} : Searching reactor for a valid version... [DEBUG] Property $ {uirdomainconstants.version}: Set of valid available versions from the reactor is [] [INFO] Property ${uirdomainconstants.version} : Leaving unchanged as 2.0.5-SNAPSHOT Can someone clear this please? TIA Add Comment   Mojo's Versions Maven Plugin / MVERSIONS-187 Changing properties (e.g. versions:update-property) doesn't work if the property it referenced at ad dependencyMangement Section I have a parent pom with a property definition: like this </properties> <prozess.commons.version>0.3.8.1-SNAPSHOT</prozess.commons.version> <prozess.service.version>0.3.4.1-SNAPSHOT</prozess.service.version> </properties> ... <build> </plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email