We use Velocity 1.5 to generate the database creation scripts for
Roller. In the latest 4.0 release candidate a PostgreSQL user had
problems because there are some null bytes in the scripts generated by
Velocity / Texen. The null bytes are not in the source templates.
Here's how we run Texen:
<texen
controlTemplate="control.vm"
contextProperties="${sql}/dbscripts.properties"
useClasspath="true"
outputDirectory="${build.dbscripts}"
outputFile="README.txt" />
I tried saving the input templates with UTF-8 encoding, but that didn't help.
I tried adding inputEncoding="UTF-8" outputEncoding="UTF-8" but that
didn't help.
Any ideas what I'm doing wrong?
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
