-
Bug
-
Resolution: Fixed
-
P4
-
hs25
-
b56
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8027489 | 8 | Volker Simonis | P4 | Resolved | Fixed | b114 |
The three XSL files
src/share/vm/trace/traceEventClasses.xsl
src/share/vm/trace/traceEventIds.xsl
src/share/vm/trace/traceTypes.xsl
contain <xsl:import> elements after <xsl:output> elements. This is not allowed, because according to the XSLT specification (http://www.w3.org/TR/xslt#element-import) "xsl:import element children must precede all other element children of an xsl:stylesheet element".
I do not know why the current OpenJDK XSLT processor doesn't object this, but other XSLT processors (i.e. the one in IBM J9) do which leads to build failures if building with a non-Oracle boot JDK.
The fix is easy - just reorder the <xsl:import> elements before the <xsl:output> elements.
src/share/vm/trace/traceEventClasses.xsl
src/share/vm/trace/traceEventIds.xsl
src/share/vm/trace/traceTypes.xsl
contain <xsl:import> elements after <xsl:output> elements. This is not allowed, because according to the XSLT specification (http://www.w3.org/TR/xslt#element-import) "xsl:import element children must precede all other element children of an xsl:stylesheet element".
I do not know why the current OpenJDK XSLT processor doesn't object this, but other XSLT processors (i.e. the one in IBM J9) do which leads to build failures if building with a non-Oracle boot JDK.
The fix is easy - just reorder the <xsl:import> elements before the <xsl:output> elements.
- backported by
-
JDK-8027489 Wrongly placed <xsl:import> element in Event-Based JVM Tracing .xsl files
-
- Resolved
-