Jeremy,
 
The original request was for a simple way to get the test cases. I am now zipping up the entire test suite (not just those few directories) since other files in it are useful. The model is like for other code we download. Doing a CVS checkout is potential dangerous since it is possible the test cases are not all correct. I do the zip after running the validation checked (part of the build). So when there is a successful build, the zip gets created at the last step.
 
However, using a zip and <get> means you have to manually delete the zip to get the new version.
 
Maybe the compromise is to check out the zip? Then you are sure you are getting a consistent set of test cases and you're always getting the latest version.

 
On 11/13/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote:

OK. Thanks for the clarification.

I think the zip will be kept up-to-date (or we can request that it be) and, shortly, the test suite should be finalized.

Arthur - comments?

Lawrence




"Jeremy Hughes" <[EMAIL PROTECTED] >
Sent by: [EMAIL PROTECTED]

11/13/2006 02:07 PM

Please respond to
[email protected]

To
[email protected]
cc
Subject
Re: w3c test files





On 11/13/06, Lawrence Mandel <[EMAIL PROTECTED] > wrote:
>
> Jeremy,
>
> By "it could prevent a lot of needless creating and checking in of new test-suite.zip files" do you mean that the zip file will be checked in to Woden's repository? If so, I think this is a mistake. I don't see the need for us to mirror the zip file locally as it's available from the W3C.

It's checked into the W3C CVS. So it's not mirrored. What I was
suggesting was for the Woden build.xml to do a direct CVS checkout of
the test files so the build env is always up to date, rather than wait
for a new test-suite.zip to be created off the latest tests and
checked in.

btw: the build.properties has this as the URL to get the test-suite.zip from:

http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/zips/test-suite.zip

Jeremy
>
>  Lawrence
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to