I'm looking at this to see if I can figure it out. However, I
recommend just going ahead and releasing. I don't think this is a
blocker.
I am also trying to figure out how to send patches. It's not clear if
there's a way to do this without a gitbox login.
Post-release I'd put a very high priority on moving to Github and/or
updating the contributor instructions. It's a force multiplier for
everything else Xalan might want to do, and essential for building a
healthy developer community.
On Sat, Feb 11, 2023 at 8:52 PM Mukul Gandhi <muk...@apache.org> wrote:
>
> Hi Gary,
> The XalanJ api tests are now running fine, and don't produce sort
> of confusing ant log statements like '[xalantest] line 1 column 147 -
> Error: <item-out> is not recognized!'.
>
> The XalanJ api tests need to be run, with build command 'build
> apitest'. This has been documented within XalanJ readme file as well.
>
> The only issue, that should be solved is following,
>
> When we run the XalanJ tests ant target as following, 'build smoketest',
>
> this produces certain log statements like following,
>
> [xalantest] line 1 column 157 - Error: <append> is not recognized!
> // log statements like these are, the area of
> concern for us just now
> [xalantest] line 1 column 177 - Error: <data> is not recognized!
> [xalantest] PASS! Redir-Append-Inner-Extension test of javaRedir2.xsl
> [xalantest] PASS! Redir-AppendOuter-Extension test of javaRedir2.xsl
> [xalantest] PASS! javaSample3 has been called 1 times
> [xalantest] PASS! Extension test of javaSample3.xsl
> [xalantest] HASHTABLE: javaSample4.postCheck() counters
> [xalantest] index=16
> [xalantest] PASS! javaSample4 has been called 31 times
> [xalantest] PASS! Extension test of javaSample4.xsl
> [xalantest] TestCaseClose(Pass) 1 Conformance test of: java
> [xalantest] TestCaseInit 2 Conformance test of: library
> [xalantest] PASS! ExtensionTestlet{trax} libraryDifference01.xsl
> [xalantest] PASS! ExtensionTestlet{trax} libraryDistinct01.xsl
>
> The confusing log statements like '[xalantest] line 1 column 157 -
> Error: <append> is not recognized!' as, cited within above logs
> example, are due to the XSL test files javaRedir2.xml and
> javaRedir2.xsl. When I run this tests XSLT transformation from command
> like following,
>
> java org.apache.xalan.xslt.Process -in javaRedir2.xml -xsl javaRedir2.xsl
>
> I don't get any errors like 'line 1 column 157 - Error: <append> is
> not recognized!'.
>
> I believe that, for example, the XalanJ test case for
> tests\extensions\java\javaRedir2.xml &
> tests\extensions\java\javaRedir2.xsl doesn't point to a bug within
> XalanJ, and the log statements like 'line 1 column 157 - Error:
> <append> is not recognized!' are coming from XalanJ tests
> implementation (the XalanJ tests ant build implementation, is
> producing these logs).
>
> I'm still unable to solve this (i.e, not producing log statements like
> '[xalantest] line 1 column 157 - Error: <append> is not recognized!'
> within XalanJ tests logs.
>
> We can either mention these facts, within XalanJ readme file and make
> a new XalanJ 2.7.3 RC, or spend more time trying to solve these issues
> (any help from any one, to help us solve these issues is definitely
> welcome).
>
> Any thoughts, please?
>
> On Sat, Feb 11, 2023 at 10:23 PM Gary Gregory <garydgreg...@gmail.com> wrote:
> >
> > Ping?
>
> >> I'm missing something:
> >>
> >> "Certain XalanJ "api" tests were causing these issues, and I've now
> >> omitted those "api" tests from XalanJ tests configuration."
> >>
> >> So when are these test run?
>
>
> --
> Regards,
> Mukul Gandhi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
> For additional commands, e-mail: dev-h...@xalan.apache.org
>
--
Elliotte Rusty Harold
elh...@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
