jcastura 01/01/11 15:36:31 Modified: test/misc README.txt Log: edits - now have user move templates into test/misc for testing so it works after getting from cvs Revision Changes Path 1.2 +7 -8 jakarta-velocity/test/misc/README.txt Index: README.txt =================================================================== RCS file: /home/cvs/jakarta-velocity/test/misc/README.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- README.txt 2000/12/02 05:57:09 1.1 +++ README.txt 2001/01/11 23:36:31 1.2 @@ -1,17 +1,16 @@ Welcome to Velocity! -The test.sh file in this directory can be used to test the templates in the test/templates folder. -The test.sh file takes one argument: the name of the Velocity template (*.vm file). The output -is put into test/misc/output. +The test.sh file in this directory can be used to render the output of Velocity templates (*.vm files). -For example, to display the output of the file test.vm, type the following at the command line: +The test.sh file takes one argument: the name of the Velocity template. The output generated by the specified template can be found in test/misc/output. - ./test.sh ../templates/test.vm +For example, to display the output of the file test/misc/test.vm, type the following at the command line: -Programmers working on Velocity will find these test files useful for testing whether changes to -the code have altered Velocity's expected behaviour. + ./test.sh test.vm -The templates in the test/templates folder supplement those presented in the examples folder. +Programmers working on Velocity will find the templates in test/templates useful for determining whether changes to the code have altered Velocity's expected behaviour. + +If the output file is empty, velocity.log will likely hold clues to the cause of the problem. Thanks for using Velocity!
