Ah. I did see that and had not investigated.
Different configuration for dev build and src build seemed surprising,
but if that's what we've got, it's working, and the docs are clear
there's no need to change it. (And if it's standard practice for Apache,
it would be hard to argue with.)
On 3/26/2023 11:11 AM, Mukul Gandhi wrote:
Hi Joseph,
On Sun, Mar 26, 2023 at 8:18 PM cc Kesselman <[email protected]> wrote:
I've certainly been running the tests with xalan-java and xalan-test as
siblings checked out into the same parent directory, and I believe that is what
the build now assumes. It also makes more sense when working with these in
Eclipse, which expects projects to be siblings.
A XalanJ developer, is expected to check-out the xalan-java and
xalan-test repos's as siblings. That's how XalanJ, builds are
organized for the developer.
For a XalanJ src distribution user, we provide the XalanJ distribution
files xalan-j_2_7_3-src.zip/xalan-j_2_7_3-src.tar.gz.
We originally agreed that, the XalanJ src distribution user, would get
the entire contents of folder xalan-test within the src.zip/tar.gz.
files. The XalanJ src distribution builds (for the implementation and
the tests) are organized around this folder structure relationship.
Firstly, the XalanJ user has to be within the src distribution root
(after user does the unzip of the XalanJ src distribution), and run
the command 'build clean fulldist' to produce the XalanJ build which
the user might want to test with XalanJ test suite. Then the XalanJ
user needs to go within the xalan-test folder (within the XalanJ src
distribution folder structure), and can run XalanJ tests from there,
as described within the XalanJ README file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
