|
Great idea.
It's always a tradeoff what to put into the site (should change rarely) and what to put into the README. But I think we should add some text and links to the contents of the TCK page: Add a link to the downloads page (which should contain all of the downloads; the user can select which version to use). This way, if you start by navigating the TCK link, you can go directly to download. Add text saying that maven 1.0.x is needed to install and run the TCK. (This is the one thing needed to bootstrap; everything else is downloaded by maven). I'd also include a link to the maven 1.0.x download and site. I found it pretty difficult to get to the maven 1.0.x info so a direct pointer to the 1.0.x stuff would be nice. Add text saying that the JDO 2.0 RI and all other dependencies will automatically be downloaded as part of the installation process. I have checked in a provisional fix (revision 393578). The link to test output contains a dummy placeholder until we can produce the final results. The link to RunRules.html brings up the page from the svn web interface, thus exhibits the funny character problem described in
zip file of test results was checked in some time ago.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
To run the Technology Compatibility Kit (TCK):
1. Download and extract the TCK source bundle
2. Follow the instructions in the Prerequisites section of README.txt.
3. Follow the procedure in RunRules.html in the TCK directory.
The text will link to README.txt and RunRules.html. There will also be a link to sample output of a test run.
I want to set up this page (except for the sample output, which we will produce when a run is free of errors) as soon as possible, because I want to link to it from the downloads and/or releases page.