The Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.3.
NOTE: This is the last release line that will support running on Maven 2.0.x.
NOTE: This version contains one method that requires JDK 1.5, version
1.3.1 of this plugin will be released tomorrow and that will run on
JDK 1.4. Version 2.0 of the plugin will require Maven 2.2.1 and JDK
1.5.
NOTE: One major change in this version is that the
versions:display-plugin-updates goal has been modified to take into
account the project and plugin's prerequisites, so that if you invoke
it on a project that specifies a minimum of Maven 2.0.9, it will only
suggest plugin updates that are compatible with that version of
Maven... oh and it will also suggest what plugin updates are available
if you increase the minimum version of Maven in your project's pom.
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.
The Mojo Team.
Release Notes - Maven 2.x Versions Plugin - Version 1.3
** Bug
* [MVERSIONS-99] - display-dependency-updates reports
dependencies with ranges under wrong heading (when the range contains
the latest version)
* [MVERSIONS-114] - Explict versions inside child poms are updated
if they are the same than the version in the parent pom
* [MVERSIONS-117] - NPE in UseLatestSnapshotsMojo when
allowMajorUpdates=true
* [MVERSIONS-120] - NPE from DefaultArtifactVersion.parseVersion
in DefaultVersionsHelper.lookupPluginUpdates
* [MVERSIONS-127] - lock-snapshots does not work on Maven 3.0-RC3
* [MVERSIONS-136] - property-updates-report contains a typo
* [MVERSIONS-140] - Version ranges in dependencies cause NPE in
versions:use-latest-versions when -Dincludes excludes the dependency
* [MVERSIONS-147] - versions:resolve-ranges isn't resolving ranges
found in properties
* [MVERSIONS-150] - resolve-ranges fails for multi-module project
with inter-module dependencies w/o doing mvn install
* [MVERSIONS-155] - display-property-updates goal displays the
updated versions twice
* [MVERSIONS-159] - IllegalStateException happens for properties
in excludeProperties if includeProperties is also set
** Improvement
* [MVERSIONS-108] - Update documentation with default values for
processDependencies/processDependencyManagement
* [MVERSIONS-139] - Need way to lock a version.
* [MVERSIONS-169] - display-plugin-updates should be aware of the
required Maven version and only suggest updates where they are
compatible with the version of maven being used to run the mojo.
** New Feature
* [MVERSIONS-31] - Compare dependency versions to a remote pom's
dependency management.
* [MVERSIONS-93] - Add "allow*" flags to use-latest-releases and
use-latest-versions similar to use-latest-snapshots
* [MVERSIONS-113] - Support interactive mode in versions:set
* [MVERSIONS-125] - Set dependencies to a specific version
* [MVERSIONS-146] - Support updating a version property on the
command-line w/o versions-maven-plugin configuration
* [MVERSIONS-149] - Re-work integration tests to use
mock-repository-maven-plugin
Share and Enjoy[1]
The Mojo Team
[1] http://www.youtube.com/watch?v=_wSBC5Dyds8
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
