On Fri, 1 Sep 2000, dave wrote:
> Jon,
>
> I haven't worked on the TDK for a little while so I'm not sure how the
> setup handles this now. But, originally this was the reason for the
> tdkhome variable in the newapp.props file. The tdkhome was set
> to the full path of your TDK installation. This value would then get
> picked up by the ant script and would set the full path in the appropriate
> properties file (specifically the wm.props file) when you created a newapp.
>
> Jason and I went back and forth as to whether it was needed or not. I felt
> it was because it didn't appear that WM handled relative paths well. He
> (Jason) can probably shed so light on how he got it to work.
I will grab the latest TDK, and give it whirl. I did get it
to work with relative paths. Let me play around and I'll
report what I find.
jvz.
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
