[mojo-dev] [jira] (MVERSIONS-261) Build doe not fail when version not found

[Steve Boardwell (JIRA)]

Title: Message Title

Steve Boardwell updated an issue   Mojo's Versions Maven Plugin / MVERSIONS-261 Build doe not fail when version not found Okay, I can see point in not wanting to break the build and I think I understand what should work and what shouldn't. Just for my own understanding, I have added a zip containing test project. There are two projects: shared-parent-pom to be used by other projects versions-maven-plugin-test-parent versions-maven-plugin-test-parent/pom.xml a project using the shared-parent-pom versions-maven-plugin-test-project versions-maven-plugin-test-project/my-first-project-module1 versions-maven-plugin-test-project/my-first-project-module1/pom.xml versions-maven-plugin-test-project/pom.xml versions:update-parent is no update available warning given, nothing changed, build successful is an update available parent version updated updated regardless of the specified version range (below version 1.0.0-100 specified, but the 2.0.0-100 was available). Or am I doing something wrong here? $ (cd versions-maven-plugin-test-project/ && mvn versions:update-parent -DnewVersion=[1.0.0-100] -DgenerateBackupPoms=false -pl .) [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building Project with shared parent pom 0.0.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- versions-maven-plugin:2.1:update-parent (default-cli) @ my-first-project --- [INFO] Updating parent from 1.0.0-100 to 2.0.0-100 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.841s [INFO] Finished at: Mon Jul 28 15:08:36 CEST 2014 [INFO] Final Memory: 10M/150M [INFO] ------------------------------------------------------------------------ versions:set The GAV modus (in my case, artifactId) is great and works like a charm, thanks. Is the following also correct? there is no check at all as to the validity or availability of the newVersion. This, I guess, is the responsibility of the person/script performing the command. how to all the filter/query options work together when using versions:set does the oldVersion property factor when also using GAV properties? It doesn't seem to make any difference apart from in the maven output. Summary The updating parent regardless of specified version seems unexpected to me. The rest may be just usage errors on my part. I'd be happy to provide some real test cases if necessary. Change By: Steve Boardwell Attachment: versions-maven-plugin-example.zip Add Comment   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