Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Le 17/11/2014 03:16, Daniel Schepler a écrit : By the way, after I built maven-jarjar-plugin with ant added, I got a similar failure building sisu-guice: I confirm this issue with a rebuilt version of velocity without a dependency on Ant. This is caused by the pom of maven-jarjar-plugin referencing ant as an optional dependency, the libmaven-jarjar-plugin-java package doesn't depend on ant and Maven is unable to resolve the dependency. maven-jarjar-plugin contains the jarjar Ant task but it doesn't seem to be used. The Ant task is already provided by the jarjar package, so I don't think libmaven-jarjar-plugin-java should depend on ant. This issue can be solved by marking the ant dependency in maven-jarjar-plugin as provided. Emmanuel Bourg __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Source: jarjar-maven-plugin Version: 1.9-2 Severity: important In my locally rebuilt repository, ant is no longer automatically pulled in by the Build-Depends of jarjar-maven-plugin (with the official package builds, it's pulled in by velocity). As a result, I'm getting this error in the build: ... 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=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven.properties -Dclassworlds.conf=/etc/maven2/m2-debian.conf org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml -Dmaven.repo.local=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven-repo package [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 JarJar Maven Plugin [INFO]task-segment: [package] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.ant:ant:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ant -DartifactId=ant -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.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 2) org.apache.ant:ant:jar:debian -- 1 required artifact is missing. for artifact: org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 from the specified remote repositories: 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] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Nov 11 18:19:57 UTC 2014 [INFO] Final Memory: 7M/149M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (I've verified that pbuilder build velocity using all official packages results in a package with Depends: libcommons-collections3-java, libcommons-lang-java (= 2.6). If that's incorrect, feel free to correct the issue in maven-debian-helper and then close this bug.) -- Daniel Schepler __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Hi Daniel, As I understand ant is pulled through maven-debian-helper-velocity-ant. How did you manage to install the build dependencies without ant installed? Ant is a direct dependency so it would be a good idea to add it to the build deps, but this error should not happen with the current dependency graph. Emmanuel Bourg __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
On 11/16/2014 09:53 AM, Emmanuel Bourg wrote: Hi Daniel, As I understand ant is pulled through maven-debian-helper-velocity-ant. How did you manage to install the build dependencies without ant installed? Ant is a direct dependency so it would be a good idea to add it to the build deps, but this error should not happen with the current dependency graph. Hi Emmanuel, I believe what Daniel is saying is that if you rebuild the entire dependency chain, ant isn't being pulled in (by velocity). Or put another way, there is a difference between the dependency graph that exists for the binary build-deps in the archive, and the dependency graph created by rebuilding all of the build-deps in the archive from source. Daniel, first, do I have that right, and secondly, is your rebuild on jessie or sid? In any event, no harm in adding ant directly, although it would be good to determine if this is a class of FTBFS bugs instead of an isolated instance. E.g., there may be other packages that were expecting velocity to pull in ant. (Theoretically, because I haven't looked into it, but velocity appears to be long overdue for some freshening...) Cheers, tony signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Daniel confirmed privately he rebuilt velocity locally. The pom.xml file in velocity has a dependency on ant with the scope 'provided'. The recent versions of maven-debian-helper no longer inject this kind of dependencies in the package dependencies (because the provided dependencies are usually satisfied at runtime by a container. This is typical with the dependencies on the Servlet and the OSGi APIs). So here the rebuilt velocity package lacks the dependency on ant and breaks jarjar-maven-plugin. Thank you for spotting this issue Daniel. I'm going to add the missing build dependency on Ant. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
On Sun, Nov 16, 2014 at 11:26 AM, tony mancill tmanc...@debian.org wrote: I believe what Daniel is saying is that if you rebuild the entire dependency chain, ant isn't being pulled in (by velocity). That's correct. Or put another way, there is a difference between the dependency graph that exists for the binary build-deps in the archive, and the dependency graph created by rebuilding all of the build-deps in the archive from source. Daniel, first, do I have that right, and secondly, is your rebuild on jessie or sid? The rebuild is based on sid. By the way, after I built maven-jarjar-plugin with ant added, I got a similar failure building sisu-guice: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.ant:ant:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ant -DartifactId=ant -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.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 2) org.apache.ant:ant:jar:debian -- 1 required artifact is missing. for artifact: org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 from the specified remote repositories: 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] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Sun Nov 16 22:29:05 UTC 2014 [INFO] Final Memory: 17M/344M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 I'm not sure why that's happening, given that as far as I can tell, the dependency on ant is marked as optional in jarjar-maven-plugin's pom.xml file. -- Daniel Schepler __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
