Re: Help to finalise libjloda-java needed

[Pierre Gruet <pgtdebian@free.fr>]

Hi again,

Le 18/11/2020 à 15:59, Pierre Gruet a écrit :
> Hi Andreas,
> 
> 
> Le 18/11/2020 à 11:09, Andreas Tille a écrit :
>> Hi Pierre (and others)
>>
>> I tried to update libjloda-java but the build fails with
>>
>> ...
>> compile:
>>     [javac] Compiling 360 source files to /build/libjloda-java-2.0/antbuild/modules/jloda
>>     [javac] error: the unnamed module reads package org.xml.sax.helpers from both java.xml and xml.apis
>>     [javac] error: the unnamed module reads package org.xml.sax.ext from both java.xml and xml.apis
>>     [javac] error: the unnamed module reads package org.xml.sax from both java.xml and xml.apis
>> ...
>>     [javac] error: the unnamed module reads package org.apache.batik.ext.awt.g2d from both batik.awt.util and batik.all
>>     [javac] error: the unnamed module reads package org.apache.batik.ext.awt.font from both batik.awt.util and batik.all
>>     [javac] error: the unnamed module reads package org.apache.batik.ext.awt.color from both batik.awt.util and batik.all
>>     [javac] 100 errors
>>
>> BUILD FAILED
>> /build/libjloda-java-2.0/antbuild/build.xml:59: Compile failed; see the compiler error output for details.
>>
>> Total time: 1 second
>> make[1]: *** [debian/rules:15: override_dh_auto_build] Fehler 1
>>
>>
>> I guess its a simple CLASSPATH issue which is easy to fix for someone
>> with more experience than I have.
>>
> 
> Yes, this is caused by the fact that several jars provide the same package.
> I'm not very used to modules with Java, but I think that, based on what
> you pasted and the contents of the package, there are two sources of
> problems:
> - the jars in the directory jars/ of the source package (which we should
> remove) : for instance one of the jars therein provides xml.apis;
> - the line
> 	<fileset dir="${jfxDir}"  includes="*.jar"/>
> in the patched antbuild/build.xml , where ${jfxdir} is /usr/share/java,
> causes all installed jars in /usr/share/java to be searched for
> modules... and libbatik-java ships a lot of subjars and one super-jar
> (batik-all.jar) which gathers them all. This is the reason for the
> errors involving batik on the last lines you pasted.
> 
> I can give it a try and keep you informed!

Good news: this is now fixed!
I have explicitly listed the necessary jars and added two missing
dependencies. Now the package builds. My changes have been pushed to Salsa.

> 
>>
>> Kind regards
>>
>>       Andreas.
>>

Best,
Pierre