Configuring Velocity engine with Texen and Ant

[Bogdan Mocanu <bo...@gmail.com>]

Hello,

I am using Velocity 1.6.2, Texen 1.0, XmlGen and Ant inside a project 
and I cannot find a way to configure the Velocity engine properties. I 
am able to configure the context properties (that is, the properties 
that are injected in the Velocity context) but not the Velocity engine 
itself.

I looked through the Velocity dev guide (the section with configuring 
the Velocity engine), then the Texen documentation (which is very 
small), then checked out the sources for Velocity 1.6.2 and Texen 1.0 
(the branch). From what I saw, it is not possible to do this because 
Texen, inside TexenTask, configures only 5-6 properties, but doesn't 
allow for injection of other overriding properties.

Is there anyone else that is using Texen in a project? Am I missing 
something?
Perhaps there is a way to place the velocity.properties file somewhere 
in the classpath, for the Velocity engine to pick it up (although I 
tried that also, and didn't worked).

Thanks for taking the time to read my question,
Bogdan Mocanu


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org

Re: Configuring Velocity engine with Texen and Ant

[Nathan Bubna <nb...@gmail.com>]

On Tue, Sep 15, 2009 at 1:20 AM, Bogdan Mocanu
<bo...@gmail.com> wrote:
> Hello,
>
> I am using Velocity 1.6.2, Texen 1.0, XmlGen and Ant inside a project and I
> cannot find a way to configure the Velocity engine properties. I am able to
> configure the context properties (that is, the properties that are injected
> in the Velocity context) but not the Velocity engine itself.
>
> I looked through the Velocity dev guide (the section with configuring the
> Velocity engine), then the Texen documentation (which is very small), then
> checked out the sources for Velocity 1.6.2 and Texen 1.0 (the branch). From
> what I saw, it is not possible to do this because Texen, inside TexenTask,
> configures only 5-6 properties, but doesn't allow for injection of other
> overriding properties.

>From what i remember the last time i looked at the Texen source, this
is true.  You may just need to alter and build Texen for yourself.

> Is there anyone else that is using Texen in a project? Am I missing
> something?
> Perhaps there is a way to place the velocity.properties file somewhere in
> the classpath, for the Velocity engine to pick it up (although I tried that
> also, and didn't worked).

Yeah, that's not currently supported, though i can't offhand think of
a reason why it shouldn't be supported.  Wanna contribute a patch?  :)

> Thanks for taking the time to read my question,
> Bogdan Mocanu
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
> For additional commands, e-mail: user-help@velocity.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org