Maven - Release Notes - Maven Ant Tasks

Maven Ant Tasks

The full list of changes can be found in our issue management system , and is reproduced below.

[MANTTASKS-13] - Ant Tasks use of authentication is inconsistent
[MANTTASKS-91] - [task dependencies]Trouble between mvn and manttasks
[MANTTASKS-103] - Can't deploy to a file: repository
[MANTTASKS-104] - files returned in sourcesFileset when no dependencies sources available
[MANTTASKS-105] - dependencies task don't read remote repositories from settings xml
[MANTTASKS-107] - repository defined in pom not used to download parent pom when defining pom reference
[MANTTASKS-108] - Maven Ant Tasks are switching the Classloader of the Main Ant Thread

The full list of changes can be found in our issue management system , and is reproduced below.

[MANTTASKS-2] - artifact:dependencies related error: No files specified for filelist
[MANTTASKS-22] - artifact:dependencies does not respect in the generated classpath the order of the dependencies
[MANTTASKS-23] - antlib:deploy doesn't set correct snapshot version
[MANTTASKS-67] - artifact:deploy - The name of deploying element in snapshot repository is wrong
[MANTTASKS-77] - offline element of settings.xml ignored by artifact:dependencies.
[MANTTASKS-78] - unable to download a dependency when it is a SNAPSHOT and multiple remoteRepositories are used
[MANTTASKS-79] - add XML encoding support for pom.xml and settings.xml
[MANTTASKS-82] - Environment variables are not resolved in settings files
[MANTTASKS-84] - VersionMapper does not work on SNAPSHOT dependencies where uniqueVersion="true"
[MANTTASKS-85] - settings config ignored for remoteRepositories not defined in pom
[MANTTASKS-87] - Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a "Error downloading parent pom" error
[MANTTASKS-98] - NPE if user settings file doesn't exist

Warning : there are 2 incompatible changes that you must know before upgrading, to fix your Ant build files:

[MANTTASKS-44]: <localRepository path="..."/> instead of <localRepository location=""/> for Ant 1.7 compatibility (location attribute is used internally by Ant 1.7)
[MANTTASKS-65]: central repository is not automatically added any more if a remoteRepository is set: the code has been changed to work as expected and documented (explicit declaration)

The full list of changes can be found in our issue management system , and is reproduced below.

[MANTTASKS-1] - dependencies ant task incorrectly handles transitive snapshot dependencies
[MANTTASKS-6] - ant artifact doesn't read settings.xml
[MANTTASKS-11] - antlib + http based repository + version range errors badly
[MANTTASKS-12] - No means of preventing ant task from querying repo1.maven.org
[MANTTASKS-15] - scp:// urls not recognised, even when wagon-ssh is installed.
[MANTTASKS-18] - filesetId does not contain all dependencies when artifact was not yet locally installed
[MANTTASKS-26] - artifact:dependencies filesetId attribute causes NPE
[MANTTASKS-65] - [PATCH] add central repository only if no remoteRepository set
[MANTTASKS-70] - m2 tasks not reentrant
[MANTTASKS-75] - [PATCH] NPE if loaded settings.xml does not contain localRepository

[MANTTASKS-44] - bootstrap of components/trunk fails with ant-1.7.0RC1
[MANTTASKS-66] - [PATCH] add more information when Ant run in verbose mode (ant -v)
[MANTTASKS-69] - [PATCH] improve sample.build.xml
[MANTTASKS-72] - Remove hardcoded groupId in install-provider task
[MANTTASKS-76] - [PATCH] update Maven Ant Tasks to Maven core 2.0.7

[MANTTASKS-24] - Not enough diagnostics if failed to validate POM
[MANTTASKS-37] - The Dependencies task of Maven Antlib should override an existing path reference instead of failing
[MANTTASKS-73] - miss RemoteRepository sub-element for tasks pom and install-provider