Bug#794897: maven-scm: 1.3-6 FTBFS without libmaven-scm-providers-java which was created in this version
Hans Joachim Desserud
debian at desserud.org
Fri Aug 7 19:25:59 UTC 2015
Source: maven-scm
Version: 1.3-6
Severity: important
Dear Maintainer,
I saw that 1.3-6 was synced from Debian unstable to the development
version of Ubuntu [1], but it failed to build [2]. Oddly enough it
didn't ran into problems before it started with javadoc, but looked
like some missing build dependency.
So I took a look in my Sid vm to check whether this issue was
reproducible there as well. Now, I wasn't able to reproduce the same
issue, so the Ubuntu issue might be caused by some packages out of
sync with Debian... However, I ran into a similar issue on Debian:
[INFO] Building Maven SCM CVS Provider - Parent
[INFO] task-segment: [javadoc:jar]
[INFO]
------------------------------------------------------------------------
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO]
------------------------------------------------------------------------
[INFO] Building Maven SCM CVS Provider TCK tests
[INFO] task-segment: [javadoc:jar]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.maven.scm:maven-scm-test:jar:1.3
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.scm
-DartifactId=maven-scm-test -Dversion=1.3 -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.maven.scm
-DartifactId=maven-scm-test -Dversion=1.3 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.maven.scm:maven-scm-provider-cvstest:jar:1.3
2) org.apache.maven.scm:maven-scm-test:jar:1.3
----------
1 required artifact is missing.
for artifact:
org.apache.maven.scm:maven-scm-provider-cvstest:jar:1.3
The missing artifact is provided by maven-scm, used to reside
in libmaven-scm-java [3], but is now part of
libmaven-scm-providers-java [4]. I am not quite sure why it failed to
find this artifact from the current build, but after installing
libmaven-scm-providers-java 1.3-6 it built succesfully. So it looks
like this might be a circular dependency or at least somethin odd
going on.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.0.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
[1] https://launchpad.net/ubuntu/+source/maven-scm/1.3-6
[2]
https://launchpadlibrarian.net/213866379/buildlog_ubuntu-wily-amd64.maven-scm_1.3-6_BUILDING.txt.gz
[3] https://packages.debian.org/stretch/all/libmaven-scm-java/filelist
[4]
https://packages.debian.org/sid/all/libmaven-scm-providers-java/filelist
--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
More information about the pkg-java-maintainers
mailing list