Hm...good job of tracking that down.
I've got a patch into velocity-dev that will let us get around this
thorny template/useClasspath issue but until then, I'll submit a patch
to handle this.
Actually, now that I look, I've got a larger patch for build-torque.xml
that fixes this issue. I'm waiting for commit access to put it in the
repository, but if you want, the approach I take in the patch is:
Use ant's condition task like:
<target name="check-use-classpath">
<condition property="torque.internal.useClasspath">
<equals arg1="${useClasspath}" arg2="true"/>
</condition>
</target>
Then change the target sql-template/sql-classpath targets by adding a
dependents="check-use-classpath" and change the if/unless from just
useClasspath to torque.internal.useClasspath which will only be set
ifuseClasspath is true.
- Stephen
> -----Original Message-----
> From: Thomas Wheeler [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 11:29 AM
> To: 'Turbine Torque Users List'
> Subject: RE: templatePath
>
> Solution found. Developers, I hope you're listening. (msegalla, I
hope
> you're listening too :).)
>
> The "sql-classpath" target was being built instead of "sql-template".
> Apparently, if sql-template is to be built, the useClassPath property
must
> be undefined (not just set to false) -- otherwise it will use the
> sql-classpath target.
>
> According to the Ant documentation, using "if" in a <target> executes
the
> target if the property is set, regardless of the value it is set to.
So the
> target
>
> <target name="sql-classpath" if="useClasspath">
>
> executes if useClasspath is set _at all_. A brief scan of the docs
doesn't
> describe this behavior.
>
> -Thomas
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
