On 15/07/2015 11:47, Mathieu Malaterre wrote:
>
> From my understanding batik-libs would be equivalent to loading each
> and every batik-* components. If so this means I broke something when
> updating to batik 1.8. Could someone with more batik experience
> please double check my batik package (check svn) and tell me what I
> did wrong ?
Hello Mathieu,
The current batik 1.8 package batik-libs.jar, batik.jar, batik-all.jar and
batik-1.8.jar are dead link.
Here is a possible reason:
debian/rules assume that the upstream jar name is batik-1.8/lib/batik-libs.jar
but if you look at the build.xml:
<target name="libs-jar" depends="init, compile, prepare-build">
<jar jarfile="${build}/lib/${project}-libs-${completeVersion}.jar">
it should be batik-1.8/lib/batik-libs-1.8.jar
Jerome (from Toulouse)
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/55a6ac1e.1090...@gmx.com
