> I must say that no other project puts so many disparate things in one CVS
> tree, and then requires getting multiple slices in order to do a complete
> build and verity the results.
I don't know. Maybe we're doing it wrong. The actual structure of our
source is not, I believe, different from Xerces... i.e. we have a single
project that has both C++ and Java source in it.
What is really different about the Xalan project is the amount and
intensity of the tests that we're trying to run. XSLT is pretty complex,
and our API is pretty wide. The amount of testing we do is out of
necessity (and is still not enough). Also, some of the other projects
have non-public tests, but we have made the decision to make our tests
public, because it's the obvious and right thing to do, and because we
believe it adds further value to the Xalan project. I also think that
Xalan is just at the cutting edge of running the kind of regression tests
that all projects ought to run... as I have stated elsewhere.
I don't think that multiple CVS checkouts is the point. The point is that
Xalan is a multi-faceted, rather complex project. Multiple CVS trees would
not change a thing, in my opinion.
It is possible that we should separate the nightly "gump" build from
nightly regression testing. But I would rather see them as an integrated
process.
-scott
"Sam Ruby"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.com> cc: (bcc: Scott Boag/CAM/Lotus)
Subject: Re: Notice: Removal of XalanJ1
source on Tuesday, 6/26
06/25/2001
10:29 PM
Please
respond to
xalan-dev
Scott Boag wrote:
>
> Yes, well, you need the tests also.
>
> xml-xalan/java to compile xml-xalan
> xml-xalan/test to run the smoketests
>
> If you try to checkout from the xml-xalan level, you'll get the C++ code
> also.
>
> If the conformance test stuff is getting too much to download (it's only
> going to get bigger), perhaps you should just run the minitest:
>
> xml-xalan/test/java
> xml-xalan/test/tests/api
> xml-xalan/test/tests/api-gold
>
> build mini-test
>
> It would, of course, be better if the full smoketest was run every night,
> but if it's sucking up too much resources, then the right thing is to
> execute the (much) simpler test.
I must say that no other project puts so many disparate things in one CVS
tree, and then requires getting multiple slices in order to do a complete
build and verity the results.
Let me think about this one some more.
- Sam Ruby
