The Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.0.

The Versions Plugin has the following goals.

    * 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.
    * versuibs: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 have been
mirrored to central.

The Mojo Team.

Release Notes - Maven 2.x Versions Plugin - Version 1.0


** Bug
    * [MVERSIONS-38] - Rulessets are not correctly loaded from http uri's
    * [MVERSIONS-39] - update-properties throws NPE if a property is
configured for updating but is not defined in the pom
    * [MVERSIONS-44] - versions:set Fails for Projects with No Dependencies
    * [MVERSIONS-45] - use-latest-versio ignores the allowSnapshots bug
    * [MVERSIONS-46] - IT it-display-dependency-updates-report-001 fails
    * [MVERSIONS-47] - IT it-display-plugin-updates-004 fails
    * [MVERSIONS-48] - IT it-update-properties-004 fails
    * [MVERSIONS-49] - IT it-update-properties-005 fails
    * [MVERSIONS-50] - remove the display-dependency-updates-report
and replace with dependency-updates-report
    * [MVERSIONS-59] - versions:display-plugin-updates fails
    * [MVERSIONS-60] - NPE in versions:dependency-updates-report
    * [MVERSIONS-61] - it-dependency-updates-report-001 fails
    * [MVERSIONS-62] - it-plugin-updates-report-001 fails
    * [MVERSIONS-63] - it-update-properties-005 fails

** Improvement
    * [MVERSIONS-23] - Add possibility to include dependencymanagement
in DisplayDependencyUpdates
    * [MVERSIONS-40] - [update-child-modules] Recursively process the
whole hierarchy
    * [MVERSIONS-57] - Refactor display-dependency-updates to use the
dependency-updates-report back-end and just format the results for the
CLI
    * [MVERSIONS-65] - Update documentation to reflect new mojos and reports

** New Feature
    * [MVERSIONS-9] - check for released versions of SNAPSHOT dependencies
    * [MVERSIONS-29] - use-next-snapshots
    * [MVERSIONS-43] - Add a mojo to set the project version
    * [MVERSIONS-52] - Add the possibility to use version range in
includes/excludes filters on use-latest-releases
    * [MVERSIONS-53] - plugin-updates-report
    * [MVERSIONS-56] - property-updates-report
    * [MVERSIONS-64] - display-property-updates mojo

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to