Re: [request to review, and vote] XalanJ 2.7.3 release candidate

Hi all, We've just published a new XalanJ 2.7.3 RC, at https://dist.apache.org/repos/dist/dev/xalan/j/2.7.3/RC3/. This incorporates a bug fix, to an issue discovered with the previous XalanJ 2.7.3 RC. The following tests, have passed with XalanJ 2.7.3 RC3, smoketest smoketest.xsltc

[jira] [Updated] (XALANJ-2638) error reporting improvement, for XalanJ interpretive processor for few of XPath parse errors, during XSLT transformation

[ https://issues.apache.org/jira/browse/XALANJ-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi updated XALANJ-2638: - Description: Here's an illustration of this issue. XML document: 105 XSLT stylesheet:

[jira] [Resolved] (XALANJ-2638) error reporting improvement, for XalanJ interpretive processor for few of XPath parse errors, during XSLT transformation

[ https://issues.apache.org/jira/browse/XALANJ-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Gandhi resolved XALANJ-2638. -- Resolution: Fixed Resolving this issue. The fix for this issue, was committed to the XalanJ

Re: [request to review, and vote] XalanJ 2.7.3 release candidate

Hi Joseph, I've analyzed about, writing a test case for this XalanJ bug. The test case for this, can't be written trivially. When the class org.apache.xalan.xslt.Process does this XSLT transform, the error messages are printed to Java System.err, due to which JUnit style 'assert' cannot be