The Maven team is pleased to announce the release of the Maven Dependency Plugin, version 2.3
This plugin is used to copy and unpack artifacts and dependencies. It also provides visualization and optimization tools for your project dependencies. http://maven.apache.org/plugins/maven-dependency-plugin/ The main change in this plugin from version 2.2 is that the "copy" and "unpack" goals will now resolve from the reactor in Maven 2.x. Initially when these goals were added to the dependency plugin, they did not resolve artifacts from the reactor. With Maven 3, however, the plugin would resolve artifacts from the reactor. The fix for MDEP-316 ensures that there is consistent behaviour when running with both Maven 2.x and Maven 3 by having the "copy" and "unpack" goals alway search for artifacts from the reactor before failing through to the local, and subsequently remote repositories. The side-effect of this is that some builds which may have been forced to set the release plugin's preparationGoals to "clean install" in order to be able to release, will now be able to revert to the preferred "clean verify". You should specify the version in your project's plugin configuration: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.3</version> </plugin> Release Notes - Maven 2.x Dependency Plugin - Version 2.3 ** Bug * [MDEP-316] - dependency:copy and dependency:unpack behave differently with M2 and M3 (should always search the reactor for artifacts) ** Improvement * [MDEP-145] - Outputting dependency resolution/tree in a well known _machine readable_ output format * [MDEP-265] - Add classifier option for dependency:get * [MDEP-315] - Add pt_BR localization Enjoy, -The Maven team --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org