Your message dated Mon, 26 Feb 2018 10:44:37 +0100 with message-id <1519638277.13887.6.ca...@physics.uu.se> and subject line Re: Bug#891217: voms-api-java FTBFS: java.lang.NoClassDefFoundError has caused the Debian Bug report #891217, regarding voms-api-java FTBFS: java.lang.NoClassDefFoundError to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 891217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: voms-api-java Version: 3.3.0-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/voms-api-java.html ... constituent[38]: file:/usr/share/maven/lib/commons-lang3.jar constituent[39]: file:/usr/share/maven/lib/commons-io.jar constituent[40]: file:/usr/share/maven/lib/commons-cli.jar constituent[41]: file:/usr/share/maven/lib/cdi-api.jar constituent[42]: file:/usr/share/maven/lib/aopalliance.jar constituent[43]: file:/usr/share/maven/conf/logging/ --------------------------------------------------- Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/cli/UnrecognizedOptionException at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:279) at org.apache.maven.cli.MavenCli.main(MavenCli.java:194) at org.apache.maven.cli.MavenCli.main(MavenCli.java:184) at org.debian.maven.Wrapper.main(Wrapper.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: java.lang.ClassNotFoundException: org.apache.commons.cli.UnrecognizedOptionException at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) ... 12 more dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/voms-api-java-3.3.0 -Dclassworlds.conf=/etc/maven/m2-debian.conf org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/voms-api-java-3.3.0/debian -Dmaven.repo.local=/build/1st/voms-api-java-3.3.0/debian/maven-repo --batch-mode package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make: *** [debian/rules:5: build] Error 1
--- End Message ---
--- Begin Message ---Control: fixed 891217 libmaven3-core-java/3.5.2-2 This is due to a missing dependency on libcommons-cli-java in libmaven3-core-java version 3.5.2-1 that was fixed in version 3.5.2-2. $ dpkg --info libmaven3-core-java_3.5.2-1_all.deb | grep Depends Depends: libatinject-jsr330-api-java, libcommons-lang3-java, libguava- java, libmaven-parent-java (>= 27), libmaven-resolver-java (>= 1.1.0), libmaven-shared-utils-java (>= 3.1.0), libplexus-classworlds-java (>= 2.5.2), libplexus-component-annotations-java (>= 1.7.1), libplexus- interpolation-java (>= 1.24), libplexus-sec-dispatcher-java (>= 1.4), libplexus-utils2-java (>= 2.x), libsisu-inject-java, libsisu-plexus- java (>= 0.3.3), libslf4j-java (>= 1.7.25), libwagon-provider-api-java (>= 3.0.0), libguice-java (>= 4.0) $ dpkg --info libmaven3-core-java_3.5.2-2_all.deb | grep Depends Depends: libatinject-jsr330-api-java, libcommons-cli-java (>= 1.4), libcommons-lang3-java, libgeronimo-annotation-1.3-spec-java, libguava- java, libguice-java (>= 4.0), libmaven-parent-java (>= 27), libmaven- resolver-java (>= 1.1.0), libmaven-shared-utils-java (>= 3.1.0), libplexus-cipher-java (>= 1.7), libplexus-classworlds-java (>= 2.5.2), libplexus-component-annotations-java (>= 1.7.1), libplexus- interpolation-java (>= 1.24), libplexus-sec-dispatcher-java (>= 1.4), libplexus-utils2-java (>= 2.x), libsisu-inject-java, libsisu-plexus- java (>= 0.3.3), libslf4j-java (>= 1.7.25), libwagon-provider-api-java (>= 3.0.0) No need to fix anything in voms-api-java. Mattias fre 2018-02-23 klockan 15:46 +0200 skrev Adrian Bunk: > Source: voms-api-java > Version: 3.3.0-1 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/voms-api-java.html > > ... > constituent[38]: file:/usr/share/maven/lib/commons-lang3.jar > constituent[39]: file:/usr/share/maven/lib/commons-io.jar > constituent[40]: file:/usr/share/maven/lib/commons-cli.jar > constituent[41]: file:/usr/share/maven/lib/cdi-api.jar > constituent[42]: file:/usr/share/maven/lib/aopalliance.jar > constituent[43]: file:/usr/share/maven/conf/logging/ > --------------------------------------------------- > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/commons/cli/UnrecognizedOptionException > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:279) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:194) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:184) > at org.debian.maven.Wrapper.main(Wrapper.java:89) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.ClassNotFoundException: > org.apache.commons.cli.UnrecognizedOptionException > at > org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at > org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 12 more > dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/build/1st/voms-api-java-3.3.0 > -Dclassworlds.conf=/etc/maven/m2-debian.conf > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml > -Ddebian.dir=/build/1st/voms-api-java-3.3.0/debian > -Dmaven.repo.local=/build/1st/voms-api-java-3.3.0/debian/maven-repo > --batch-mode package javadoc:jar javadoc:aggregate -DskipTests > -Dnotimestamp=true -Dlocale=en_US returned exit code 1 > make: *** [debian/rules:5: build] Error 1signature.asc
Description: This is a digitally signed message part
--- End Message ---