Bug#906375: libitext5-java: FTBFS in buster/sid (method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types)

[Jochen Sprickerhof]

Hi,

I looked into this, but haven't found an easy solution.

* Santiago Vila <sanvila at debian.org> [2018-08-17 11:20]:
>[ERROR] /<<PKGBUILDDIR>>/src/main/java/com/itextpdf/text/pdf/security/MakeXmlSignature.java:[443,22] method marshal in class org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignature cannot be applied to given types;
>  required: org.apache.jcp.xml.dsig.internal.dom.XmlWriter,java.lang.String,javax.xml.crypto.XMLCryptoContext
>  found: org.w3c.dom.Node,org.w3c.dom.Node,java.lang.String,javax.xml.crypto.dsig.dom.DOMSignContext
>  reason: actual and formal argument lists differ in length

The problem is that libitext5-java is using an internal API of 
libxml-security-java here which was reworked in version 2. Discussion 
and patch can be found here:

https://issues.apache.org/jira/browse/SANTUARIO-349

Problem is that it introduces a new class Marshaller, used to generate 
the same result as needed by libitext5-java but it's not public, so we 
can't access it easily.

Itext has moved on to version 7 in the meantime, not use the internal 
API, as far as I've seen. But it has a different API itself, so we would 
have to port all depending packages to it (which are figtree, hibiscus 
and umlet).

I'm not sure if I will find time for this soon, so help would be very 
welcome here.

As a quick fix we could probably hack around the visibility modifiers of 
Marshaller, but I guess that would be rather ugly. Just mentioning it 
for completeness.

* Andreas Tille <andreas at fam-tille.de> [2018-08-25 17:44]:
>[INFO] Scanning for projects...
>[ERROR] [ERROR] Some problems were encountered while processing the POMs:
>[FATAL] Non-resolvable parent POM for com.itextpdf:itextpdf:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11
>[FATAL] Non-resolvable parent POM for com.itextpdf:itext-pdfa:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11
>[FATAL] Non-resolvable parent POM for com.itextpdf:itext-xtra:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11
>[FATAL] Non-resolvable parent POM for com.itextpdf.tool:xmlworker:5.5.13: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact com.itextpdf:itext-parent:pom:1.0.0 has not been downloaded from it before. and 'parent.relativePath' points at no local POM @ line 5, column 11
> @
>[ERROR] The build could not read 4 projects -> [Help 1]

I've looked into this as well and have some patches to make it work up 
to the same error this bug is about. If you still want to have them, I 
can send a pull request.

Cheers Jochen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20180828/b2532dfa/attachment.sig>