On 11/4/02 11:33 AM, "Laurie Harper" <[EMAIL PROTECTED]> wrote: > I tried copying velocity.properties from the Velocity distribution into my > classes directory and got exceptions on startup, so I figured I'd look into > improving the integration at some point. I just haven't had time to look at > that yet.
So I took a look at this and discovered the code was doing exactly what I planned to add: passing all the velocity service configuration into Velocity. The 'ugly' code is just translating paths into correct absolute values; at the end of that, everything gets passed through. So I took another look at things and found that the reason the properties I added didn't work was because I used the wrong names. I was using the names Velocity logs, which turn out not to be correct. Using the right property names seems to do the trick, mostly. Global macro library re-loading still isn't working, but that seems to be a Velocity issue so I'll take it to the velocity list :-) Thanks for the help, L. -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
