Chris,
I finally got around to switching to the method you provided below. This is
way better than what I was doing.
Thanks for pointing me in the right direction.
Scott
> From: "Chris Campbell" <[EMAIL PROTECTED]>
> Reply-To: "Turbine Users List" <[EMAIL PROTECTED]>
> Date: Mon, 18 Mar 2002 11:11:14 -0800
> To: "Turbine Users List" <[EMAIL PROTECTED]>
> Subject: RE: Overriding properties defined in TR.props
>
> Use the tools supplied - ant in this case
>
> If you put an entry in your deploy target like this
>
> <filter filtersfile="${env.DEPLOY_FILTER}"/>
>
> <copy todir="${dest}/conf" overwrite="on" filtering="true">
> <fileset dir="${dir}/conf">
> <exclude name="CVS"/>
> </fileset>
> </copy>
>
>
> ( you will have to monkey around with your own targets in build.xml,
> there is alot of different ways to do this, this is just a simple
> example )
>
> where DEPLOY_FILTER is an environment variable indicating a path to a
> java style properties file
> that has entries like this:
>
> PROP1=val1
> PROP2=val2
>
> then in your TR.props you can do this
>
> database.default.driver=@PROP1@
> database.default.url=@PROP2@
>
> Just change the DEPLOY_FILTER environment variable when you build the
> war file and voila!
>
> Works great for me, I deploy to 4 different environments on many
> different OS no problem. I have the filter files checked in to cvs so i
> can deploy to any environment i have on demand with zero effort.
>
> chris c
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
