ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46612] ant -diagnostics should talk about the XSLT processor
Date Wed, 28 Jan 2009 16:43:54 GMT

Stefan Bodewig <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |
            Summary|bug in default XSLT         |ant -diagnostics should talk
                   |processor: Predicate ignored|about the XSLT processor
                   |for self::some_qname        |

--- Comment #5 from Stefan Bodewig <>  2009-01-28 08:43:52 PST ---
Sorry if I sounded too harsh.

If you run "ant -diagnostics" it may help you - hmm, I just now realize it only
talks about the XML parser but not the XSLT processor, reopening because of

The XSLT task allows you to configure the factory, that's why I talked about
it.  Yes, the default is to go with whatever the system provides.

What the system provides depends on your vendor.  Sun has decided to ship a
(pretty old and buggy) version of XSLTC, a variant of Apache Xalan-J that
doesn't seem to become Xalan's main line anytime as their processor with Java5
and I think they still do with Java6.  I may be wrong, though.

Point 13 in is the best hint
I can give.  See also point 9 of that list.

I happen to be involved with XMLUnit as well and we've gotten lots of problem
reports because of Java5's XSLT processor.  I've come to the conclusion to
recommend the endorsed standards mechanism and the latest release of Xalan or
Saxon to anybody doing XSLT since the default in Sun classlibs is seriously
broken (and you've just hit one symptom).

I've resolved it as INVALID because it is not an Ant bug.  We (the Ant
community) don't think of the JDK as our upstream and even if we did, since we
don't bundle a JDK and have different release cycles this would be impossible
to track.

The problem you see likely doesn't affect people using Apple's JVM on a Mac,
IBM's on anything, OpenJDK 6 or Apache Harmony, for example (they will see
different bugs).

IMHO there is a difference between a distribution that bundles packages and a
single package that happens to depend on another package which may be provided
by several different "vendors".

And no, we wouldn't track an issue in Xerces (which happens to be the default
parser for most JDKs - in different versions, of course) here either.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message