Source: maven-hpi-plugin Version: 1.93-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140601 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > test -x debian/rules > mkdir -p "." > /usr/share/maven-debian-helper/copy-repo.sh /«PKGBUILDDIR»/debian > mh_patchpoms -plibmaven-hpi-plugin-java --debian-build --keep-pom-version > --maven-repo=/«PKGBUILDDIR»/debian/maven-repo > touch debian/stamp-poms-patched > # before-build target may be used to unpatch the pom files, so we need to > check if > # patching the pom files is needed here, normally not > if [ ! -f pom.xml.save ]; then \ > /usr/bin/make -f debian/rules patch-poms; \ > fi > cd . && /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar > -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties > -Dclassworlds.conf=/etc/maven2/m2-debian.conf > org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml > -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo -e package > + Error stacktraces are turned on. > [INFO] > NOTE: Maven is executing in offline mode. Any artifacts not already in your > local > repository will be inaccessible. > > [INFO] Scanning for projects... > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Maven Jenkins Plugin > [INFO] task-segment: [package] > [INFO] > ------------------------------------------------------------------------ > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.codehaus.groovy:groovy-all:jar:debian > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.codehaus.groovy > -DartifactId=groovy-all -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=org.codehaus.groovy > -DartifactId=groovy-all -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file > -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > 2) org.kohsuke.stapler:stapler-groovy:jar:debian > 3) org.codehaus.groovy:groovy-all:jar:debian > > ---------- > 1 required artifact is missing. > > for artifact: > org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > > from the specified remote repositories: > repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/), > central (http://repo1.maven.org/maven2) > > > > NOTE: Maven is executing in offline mode. Any artifacts not already in your > local > repository will be inaccessible. > > > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Missing: > ---------- > 1) org.codehaus.groovy:groovy-all:jar:debian > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.codehaus.groovy > -DartifactId=groovy-all -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=org.codehaus.groovy > -DartifactId=groovy-all -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file > -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > 2) org.kohsuke.stapler:stapler-groovy:jar:debian > 3) org.codehaus.groovy:groovy-all:jar:debian > > ---------- > 1 required artifact is missing. > > for artifact: > org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > > from the specified remote repositories: > repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/), > central (http://repo1.maven.org/maven2) > > > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at org.debian.maven.Wrapper.main(Wrapper.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: > org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: > Missing: > ---------- > 1) org.codehaus.groovy:groovy-all:jar:debian > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.codehaus.groovy > -DartifactId=groovy-all -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=org.codehaus.groovy > -DartifactId=groovy-all -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file > -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > 2) org.kohsuke.stapler:stapler-groovy:jar:debian > 3) org.codehaus.groovy:groovy-all:jar:debian > > ---------- > 1 required artifact is missing. > > for artifact: > org.jenkins-ci.tools:maven-hpi-plugin:maven-plugin:1.93 > > from the specified remote repositories: > repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/), > central (http://repo1.maven.org/maven2) > > > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 18 more > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 1 second > [INFO] Finished at: Sun Jun 01 22:34:28 UTC 2014 > [INFO] Final Memory: 8M/145M > [INFO] > ------------------------------------------------------------------------ > make: *** [mvn-build] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/06/01/maven-hpi-plugin_1.93-1_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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
