Bug#713269: maven: FTBFS: rm: cannot remove './maven-ant-tasks-2.1.1.jar': No such file or directory

[Lucas Nussbaum]

Source: maven
Version: 3.0.4-6
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  debian/rules build
> test -x debian/rules
> install -d ./debian/tmp/maven-repo
> cp -rL /usr/share/maven-repo/* ./debian/tmp/maven-repo/
> rm ./maven-ant-tasks-2.1.1.jar
> rm: cannot remove './maven-ant-tasks-2.1.1.jar': No such file or directory
> make: [makebuilddir/maven] Error 1 (ignored)
> ln -s /usr/share/java/maven-ant-tasks.jar ./maven-ant-tasks-2.1.1.jar
> mkdir -p "."
> mh_patchpoms -pmaven
> cd . && /usr/lib/jvm/default-java/bin/java -classpath /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/lib/jvm/default-java/lib/tools.jar  -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dpackage=maven -Dversion=3.0.4 -Dmaven.home=/usr/share/maven2/ -Dmaven.repo.local=/«PKGBUILDDIR»/debian/tmp/maven-repo -Dmaven.test.skip=true     maven-compile
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> initTaskDefs:
>      [echo] Building Apache Maven ...
> 
> isMavenHomeSet:
> 
> init:
>      [echo] maven.home = /usr/share/maven2/
>      [echo] maven.repo.local = /«PKGBUILDDIR»/debian/tmp/maven-repo
>      [echo] distributionId = apache-maven
>      [echo] distributionName = Apache Maven
>      [echo] distributionDirectory = apache-maven
> 
> pull:
>      [copy] Copying 1 file to /«PKGBUILDDIR»
>    [delete] Deleting: /«PKGBUILDDIR»/dependencies.xml
> [artifact:dependencies] Downloading: backport-util-concurrent/backport-util-concurrent/debian/backport-util-concurrent-debian.pom from repository central at http://repo1.maven.org/maven2
> [artifact:dependencies] Unable to locate resource in repository
> [artifact:dependencies] [INFO] Unable to find resource 'backport-util-concurrent:backport-util-concurrent:pom:debian' in repository central (http://repo1.maven.org/maven2)
> [artifact:dependencies] Downloading: backport-util-concurrent/backport-util-concurrent/debian/backport-util-concurrent-debian.jar from repository central at http://repo1.maven.org/maven2
> [artifact:dependencies] Unable to locate resource in repository
> [artifact:dependencies] [INFO] Unable to find resource 'backport-util-concurrent:backport-util-concurrent:jar:debian' in repository central (http://repo1.maven.org/maven2)
> [artifact:dependencies] An error has occurred while processing the Maven artifact tasks.
> [artifact:dependencies]  Diagnosis:
> [artifact:dependencies] 
> [artifact:dependencies] Unable to resolve artifact: Missing:
> [artifact:dependencies] ----------
> [artifact:dependencies] 1) backport-util-concurrent:backport-util-concurrent:jar:debian
> [artifact:dependencies] 
> [artifact:dependencies]   Try downloading the file manually from the project website.
> [artifact:dependencies] 
> [artifact:dependencies]   Then, install it using the command: 
> [artifact:dependencies]       mvn install:install-file -DgroupId=backport-util-concurrent -DartifactId=backport-util-concurrent -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file
> [artifact:dependencies] 
> [artifact:dependencies]   Alternatively, if you host your own repository you can deploy the file there: 
> [artifact:dependencies]       mvn deploy:deploy-file -DgroupId=backport-util-concurrent -DartifactId=backport-util-concurrent -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> [artifact:dependencies] 
> [artifact:dependencies]   Path to dependency: 
> [artifact:dependencies]   	1) org.apache.maven:super-pom:pom:2.0
> [artifact:dependencies]   	2) org.codehaus.plexus:plexus-component-metadata:jar:1.5.5
> [artifact:dependencies]   	3) org.apache.maven:maven-project:jar:debian
> [artifact:dependencies]   	4) org.apache.maven:maven-artifact-manager:jar:debian
> [artifact:dependencies]   	5) backport-util-concurrent:backport-util-concurrent:jar:debian
> [artifact:dependencies] 
> [artifact:dependencies] ----------
> [artifact:dependencies] 1 required artifact is missing.
> [artifact:dependencies] 
> [artifact:dependencies] for artifact: 
> [artifact:dependencies]   org.apache.maven:super-pom:pom:2.0
> [artifact:dependencies] 
> [artifact:dependencies] from the specified remote repositories:
> [artifact:dependencies]   central (http://repo1.maven.org/maven2)
> [artifact:dependencies] 
> [artifact:dependencies] 
> 
> BUILD FAILED
> /«PKGBUILDDIR»/build.xml:115: Unable to resolve artifact: Missing:
> ----------
> 1) backport-util-concurrent:backport-util-concurrent:jar:debian
> 
>   Try downloading the file manually from the project website.
> 
>   Then, install it using the command: 
>       mvn install:install-file -DgroupId=backport-util-concurrent -DartifactId=backport-util-concurrent -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file
> 
>   Alternatively, if you host your own repository you can deploy the file there: 
>       mvn deploy:deploy-file -DgroupId=backport-util-concurrent -DartifactId=backport-util-concurrent -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 
>   Path to dependency: 
>   	1) org.apache.maven:super-pom:pom:2.0
>   	2) org.codehaus.plexus:plexus-component-metadata:jar:1.5.5
>   	3) org.apache.maven:maven-project:jar:debian
>   	4) org.apache.maven:maven-artifact-manager:jar:debian
>   	5) backport-util-concurrent:backport-util-concurrent:jar:debian
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact: 
>   org.apache.maven:super-pom:pom:2.0
> 
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> 
> 
> 
> Total time: 3 seconds
> make: *** [debian/stamp-ant-build] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/maven_3.0.4-6_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.