Le 29/10/2018 à 13:08, Erich Schubert a écrit :
> This precise bug has been fixed, as can be seen from the changelog and
> this patch:
>
> https://sources.debian.org/src/elki/0.7.1-9/debian/patches/java9-classloader.patch/
Thank you for the reference, I should have checked the patches, sorry.
Processing commands for cont...@bugs.debian.org:
> close 895695
Bug #895695 [src:elki] elki FTBFS:
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to
java.base/java.net.URLClassLoader
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need
close 895695
thanks
Building with openjdk-8 is different issue. Maven was broken with Java
11 back then within its dependencies (but #903769 is supposedly fixed
now, so building with Java 11 should work) and Maven would NPE; the ELKI
code was already made compatible with Java 11.
This
Control: reopen -1
Control: notfixed -1 0.7.1-7
Control: user debian-j...@lists.debian.org
Control: usertag -1 + default-java9
Control: tags -1 + sid buster fixed-upstream
I'm reopening the bug because the compatibility with Java 9 and later
wasn't really fixed, the JDK was just reverted to
Caused by Java 1.9, can probably be cherry-picked:
Fixed upstream, but no new release yet.
https://github.com/elki-project/elki/commit/92c96858616581c2109d36488e96c84c72d8bbc7
Am 14.04.2018 um 21:37 schrieb Adrian Bunk:
Source: elki
Version: 0.7.1-6
Severity: serious
Source: elki
Version: 0.7.1-6
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/elki.html
...
[INFO] --- exec-maven-plugin:1.6.0:exec (generate-javadoc-parameters) @ elki ---
Exception in thread "main" java.lang.ExceptionInInitializerError
at
6 matches
Mail list logo