Bug#799990: Bug#794214: org.apache.batik.dom.svg.SVGDOMImplementation

2015-10-25 Thread Erich Schubert
Hello, Sorry, I'm still very much overworked. Packaging the next version requires some effort because the build system was switched from ant to maven for the new version; furthermore I don't keep the gpg key on my usual work machines but I have to power up an older desktop instead. So I figured

Bug#794214: org.apache.batik.dom.svg.SVGDOMImplementation

2015-08-17 Thread Erich Schubert
Hello Mathieu, The annoying part is that even the Batik documentation still contains the old package name: https://xmlgraphics.apache.org/batik/using/dom-api.html It is well possible that many of the dependencies do not use this class. I'm not sure if there might be indirect dependencies that

Bug#794214: org.apache.batik.dom.svg.SVGDOMImplementation

2015-08-16 Thread Mathieu Malaterre
On Sun, Aug 16, 2015 at 1:53 PM, Erich Schubert er...@debian.org wrote: Hi, ELKI now tries to load the class dynamically, from different packages. I don't know if this is the proper way to get the DOM implementation, but it was the only one I got working. It is not yet fixed in the Debian

Bug#794214: org.apache.batik.dom.svg.SVGDOMImplementation

2015-08-16 Thread Mathieu Malaterre
Erich, Thanks for the report about batik API compat. Could you be a little more verbose on what was needed to fix ELKI ? I see that that import org.apache.batik.dom.svg.SVGDOMImplementation; is still used in the ELKI (from sid). I am trying to understand if this is possible to upload 1.8 to