It appears that the torque-sql task (and others) is not using ant's
${basedir} property like I think it should be, but is instead using the
base java directory. This is a problem in situations like the one below:
I am calling the init target of the newapp from another build file like
this:
<target name="init-app" depends="init"
description="Gen source code and SQL and ***RECREATE THE DB
TABLES***.">
<ant dir="web/myapp/WEB-INF/build" target="init" />
</target>
The dir= argument above sets the ${basedir} property correctly, but
torque-sql still looks for the turbine-schema.xml file in the conf
directory in the directory of the original build file. I get the
following error. Can anyone vouch for this? If so, how easily can this
be fixed?
turbine-sql:
[echo] +------------------------------------------+
[echo] | |
[echo] | Generating SQL for Turbine base system! |
[echo] | |
[echo] +------------------------------------------+
[torque-sql] D:\home\ipn\web\ipn\WEB-INF\src\sql\turbine-schema.sql
[torque-sql] java.io.FileNotFoundException: ../conf/turbine-schema.xml
(The system cannot find the path specified)
[torque-sql] at java.io.FileInputStream.open(Native Method)
[torque-sql] at java.io.FileInputStream.<init>(FileInputStream.java:64)
[torque-sql] at java.io.FileReader.<init>(FileReader.java:38)
Thanks,
Jonathan Carlson
[EMAIL PROTECTED]
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
