Bug 179926 – migration to xalan-serializer

• Product: Gentoo Linux
• Status: RESOLVED CANTFIX

[Description Vlastimil Babka (Caster) (RETIRED) 2007-05-26 22:04:23 UTC]

Now that bug 156258 is solved, we can start migrating stuff depending directly on serializer.jar from xalan to the new xalan-serializer package. I know at least openoffice uses it. Currently the split xalan is still backward compatible by including the external serializer.jar in own CLASSPATH and having symlink to it in /lib. That can be removed after every reverse dep is checked.

Filling this so it's not forgotten.

[Comment 1 James Le Cuirot 2015-06-30 11:09:31 UTC]

Some of the backwards compatibility has now been removed as only wss4j in the overlay, which is now gone, was directly referencing serializer.jar. I still have xalan-serializer as an RDEPEND. I'm not certain if this is necessary but it also adds a degree of backwards compatibility. We'll have to keep an eye out for packages that only require the serializer.

[Comment 2 John Gibson 2015-07-17 19:38:45 UTC]

I've discovered that dev-java/ant-apache-xalan2 now fails to emerge (at least in prefixed portage) because it can't find the class org.apache.xml.serializer.SerializerTrace. Adding a dependency upon xalan-serializer and linking in the jar solves the issue. I'm guessing that this is due to the backwards compatibility changes mentioned by James.

Should I open a new bug for this issue?

[Comment 3 James Le Cuirot 2015-07-17 20:59:44 UTC]

John, please file a new issue as I can't reproduce it here.

[Comment 4 John Gibson 2015-08-03 14:01:28 UTC]

Hi James, I filed the new bug (with a patch to fix it) 556584:
https://bugs.gentoo.org/show_bug.cgi?id=556584

It turned out to be Java 8's stricter compilation requirements. I suspect that you may see similar errors in other packages if they have minimal classpaths.

[Comment 5 Volkmar W. Pogatzki 2023-09-17 14:27:21 UTC]

Presently none of the comsumers of dev-java/xalan can be built with only the serializer. Closing.