Borrowed from this page: http://maven.40175.n5.nabble.com/error-while-deploying-a-project-td4312935.html
"Nexus 1.9 is serving up the latest format of maven metadata (see http://jira.codehaus.org/browse/MNG-4452 for some background)
If you update to Maven 2.0.10 then it can handle the additional entries and the problem should go away."
Needed change...
Index: bootstrap/build_includes.xml
===================================================================
— bootstrap/build_includes.xml (revision 25645)
+++ bootstrap/build_includes.xml (working copy)
@@ -29,7 +29,7 @@
<typedef resource="org/apache/maven/artifact/ant/antlib.xml" uri="urn:maven-artifact-ant">
<classpath>
<pathelement location="${imported.basedir}/lib/maven-ant-tasks-2.0.9.jar" />
+ <pathelement location="${imported.basedir}/lib/maven-ant-tasks-2.0.10.jar" />
</classpath>
</typedef>
Index: bootstrap/lib/maven-ant-tasks-2.0.10.jar
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
Property changes on: bootstrap\lib\maven-ant-tasks-2.0.10.jar
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Index: bootstrap/lib/maven-ant-tasks-2.0.9.jar
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream
looks like an easy fix, can you apply it to the 3.0 and 3.1 patches branches?
I can, just ran out of time yesterday.
Committed for both rel-3-1-patches and rel-3-0-patches