Someone please help me from navigating through the forest of no return, that is Google, and tell me how to force our projects back to using the older 1.2 version of the Versions plugin, instead of this newer 2.0 version which is now giving us null pointer exceptions with this simple command:
mvn -U versions:set -DnewVersion=12345 I don't really know anything about maven myself, I only plugin what the devs give me into our build configuration system. Can I make a global setting in the settings.xml, or does it have to be in each project's pom.xml? Dennis Wheeler Release Engineer II ADP Digital Marketing Solutions p 206.219.8049 | c 206.375.6781 | e dwhee...@cobalt.com <http://www.cobalt.com/> Join the conversation facebook <http://www.facebook.com/#!/adpdmc>| twitter <http://twitter.com/#!/adp_cobalt> | blog <http://www.digitalmileage.com/> This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the message and any attachments from your system. On 11/27/12 5:57 AM, "Stephen Connolly" <stephen.alan.conno...@gmail.com> wrote: >The Mojo team is pleased to announce the release of the Versions >Maven Plugin, version 2.0 > >NOTE: This release requires Maven 2.2.1 or newer and consequently JRE 1.5 >or newer. > >NOTE: This is the *last* planned release that will support running on >Maven >2.2.x > >The Versions Plugin has the following goals. > >* versions:compare-dependencies compares the dependency versions of >the current project to the dependency management section of a remote >project. >* versions:display-dependency-updates scans a project's dependencies >and produces a report of those dependencies which have newer versions >available. >* versions:display-plugin-updates scans a project's plugins and >produces a report of those plugins which have newer versions >available. >* versions:display-property-updates scans a projectand produces a >report of those properties which are used to control artifact versions >and which properies have newer versions available. >* versions:update-parent updates the parent section of a project so >that it references the newest available version. For example, if you >use a corporate root POM, this goal can be helpful if you need to >ensure you are using the latest version of the corporate root POM. >* versions:update-properties updates properties defined in a project >so that they correspond to the latest available version of specific >dependencies. This can be useful if a suite of dependencies must all >be locked to one version. >* versions:update-child-modules updates the parent section of the >child modules of a project so the version matches the version of the >current project. For example, if you have an aggregator pom that is >also the parent for the projects that it aggregates and the children >and parent versions get out of sync, this mojo can help fix the >versions of the child modules. (Note you may need to invoke Maven with >the -N option in order to run this goal if your project is broken so >badly that it cannot build because of the version mis-match). >* versions:lock-snapshots searches the pom for all -SNAPSHOT versions >and replaces them with the current timestamp version of that >-SNAPSHOT, e.g. -20090327.172306-4 >* versions:unlock-snapshots searches the pom for all timestamp locked >snapshot versions and replaces them with -SNAPSHOT. >* versions:resolve-ranges finds dependencies using version ranges and >resolves the range to the specific version being used. >* versions:set can be used to set the project version from the command >line. >* versions:use-releases searches the pom for all -SNAPSHOT versions >which have been released and replaces them with the corresponding >release version. >* versions:use-next-releases searches the pom for all non-SNAPSHOT >versions which have been a newer release and replaces them with the >next release version. >* versions:use-latest-releases searches the pom for all non-SNAPSHOT >versions which have been a newer release and replaces them with the >latest release version. >* versions:use-next-snapshots searches the pom for all non-SNAPSHOT >versions which have been a newer -SNAPSHOT version and replaces them >with the next -SNAPSHOT version. >* versions:use-latest-snapshots searches the pom for all non-SNAPSHOT >versions which have been a newer -SNAPSHOT version and replaces them >with the latest -SNAPSHOT version. >* versions:use-next-versions searches the pom for all versions which >have been a newer version and replaces them with the next version. >* versions:use-latest-versions searches the pom for all versions which >have been a newer version and replaces them with the latest version. >* versions:commit removes the pom.xml.versionsBackup files. Forms one >half of the built-in "Poor Man's SCM". >* versions:revert restores the pom.xml files from the >pom.xml.versionsBackup files. Forms one half of the built-in "Poor >Man's SCM". > >The artifacts have been deployed to the mojo repository and will be >mirrored to central. > >Release Notes - Maven 2.x Versions Plugin - Version 2.0 > >** Bug > * [MVERSIONS-150] - resolve-ranges fails for multi-module project with >inter-module dependencies w/o doing mvn install > * [MVERSIONS-166] - NPE Generating "Plugin Updates Report" report. > * [MVERSIONS-177] - versions:resolve-ranges does not change the pom >file > * [MVERSIONS-179] - Versions in dependencyManagement not updated > * [MVERSIONS-190] - resolve-ranges goal doesn't resolve ranges for >artifacts with '${project.groupId}' groupId > * [MVERSIONS-197] - resolve-ranges fails for managed-dependencies in >multi-module project > >** Improvement > * [MVERSIONS-195] - Switch to Maven 2.2.1 and Java 1.5 as minimum > >** New Feature > * [MVERSIONS-144] - Allow excluding certain versions of artifacts > > >Share and Enjoy[1] > >The Mojo Team > >[1] The Hitchhiker's Guide to the Galaxy: Share and Enjoy This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
