jvanzyl 01/08/29 09:37:08
Modified: test/texen-classpath/jar-contents Control.vm
Log:
- pull in a properties file, we will now allow a properties file to
be specified somewhere in the template path or classpath. we will
preserve the original behaviour because people might be pulling
properties files from anywhere, but we will move toward having the
props used for generation somewhere in the template path or class
path. this will help with generation being performed with everything
in a JAR.
the way the db.props files are set up in torque makes working from
a JAR not possible right now, but i will fix this today.
Revision Changes Path
1.2 +2 -0 jakarta-velocity/test/texen-classpath/jar-contents/Control.vm
Index: Control.vm
===================================================================
RCS file: /home/cvs/jakarta-velocity/test/texen-classpath/jar-contents/Control.vm,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Control.vm 2001/08/29 15:33:10 1.1
+++ Control.vm 2001/08/29 16:37:08 1.2
@@ -9,3 +9,5 @@
#set ( $sourceFile = "Test.txt" )
$generator.parse("Test.vm",$sourceFile)
+
+#set ( $dbprops = $properties.load("test.props") )