Le 29/09/2018 à 15:27, Eric Covener a écrit :
As per Xalan documentation, the JDK or JRE 1.3.x (2000), 1.4.x (2002),
or 5.x (2004) is required.
As per our doc build documentation, we need at least Java 1.2 (1998) to
build the doc.
Java 8 (2014) is LTS and is supported until 2025
Java 9 (2017)
Java 10 (2018)
Java 11 (2018) is apparently LTS
They don't mean minimums?
Later major JDK's (oracle, IBM) seem to all forks of xalan as the
default transformer, which might explain why there are few
contemporary releases.
Do we need to bring our own at all? Sticking with JDK interfaces has
some benefits.
I've investigate this.
1.6.5 Ant docs state that we need Xalan or another XSLT engine only if
we are using a version of Java older than 1.4.
I guess we can safely assume it is the case nowadays.
However, just removing the Xalan stuff from the lib directory does not
work.
There are some warnings and errors when building.
According to google, the warnings are more or less expected and can be
silently ignored, but the errors break the build process.
First error to trigger is (sory for the mix of English and French):
[xslt] : Fatal Error! Erreur lors de la vérification du type de
l'expression 'filter-expr(funcall(current, []),
[pred(=(step("attribute", 39), literal-expr(section)))])'. Cause: Erreur
lors de la vérification du type de l'expression
'filter-expr(funcall(current, []), [pred(=(step("attribute", 39),
literal-expr(section)))])'.
This is apparently related to synopsys.sxl.
If I comment:
<xsl:include href="synopsis.xsl" />
in common.xsl, I then get another error:
docs/manual/build/build.xml:383: Fatal error during transformation
using /home/tititou36/svn_httpd_trunk/docs/manual/style/manual.en.xsl:
Erreur lors de la vérification du type de l'expression
'com.sun.org.apache.xalan.internal.xsltc.compiler.ForEach@329dbdbf'.
This one looks related to:
<xsl:for-each select="httpd:override-classes($directives)">
in overrideindex.xsl
The lack of useful (at least to me) diagnostic, makes it hard to find
the root cause of this issues.
Adding -v to the Ant command line doesn't help much either.
So, if any one more used to the Xalan implementation provided in the JDK
could have a look or at least give some pointers, it would be great.
Based on my own tests, and searches, I won't be in any help with this
approach.
The drop-in replacement with Saxon gives much less troubles. :)
CJ
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
