You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Steve Cohen <sc...@javactivity.org> on 2012/01/28 03:21:57 UTC
standalone template validation
I would like to validate a template standalone.
I have a template that is giving me errors and since there is a
non-trivial build-deploy cycle to get it to run in my application I
would like a way to validate the template file itself at the command line.
I have found this:
http://code.google.com/p/velocity-validator/
but it appears to be non-functional. When run as directed it exits
immediately telling me to supply a good log4j configuration. I try to
supply one (but even this seems excessive for a standalone tool) to no
avail.
What is best way forward here?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org
Re: standalone template validation
Posted by Steve Cohen <sc...@javactivity.org>.
After having been in touch with the developer of
http://code.google.com/p/velocity-validator/, I now find this to be an
effective solution for my needs. He has added a "verbose" mode that
will produce output when a file is valid as well as when it is invalid.
I recommend it.
On 01/29/2012 03:04 PM, Guillaume Polet wrote:
> not sure it is much help here but:
>
> There are two Eclipse plugin that validates the templates directly:
> http://code.google.com/p/veloeclipse/
> http://veloedit.sourceforge.net/
>
> Otherwise you can write your own Java class to parse the template. If
> recall correctly, this is not too complex to do and the velocity parser
> should give you more details onto what is not right.
>
> Cheers,
> Guillaume
>
> Le 28/01/2012 03:21, Steve Cohen a écrit :
>> I would like to validate a template standalone.
>>
>> I have a template that is giving me errors and since there is a
>> non-trivial build-deploy cycle to get it to run in my application I
>> would like a way to validate the template file itself at the command
>> line.
>>
>> I have found this:
>>
>> http://code.google.com/p/velocity-validator/
>> but it appears to be non-functional. When run as directed it exits
>> immediately telling me to supply a good log4j configuration. I try to
>> supply one (but even this seems excessive for a standalone tool) to no
>> avail.
>>
>> What is best way forward here?
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@velocity.apache.org
For additional commands, e-mail: user-help@velocity.apache.org
Re: standalone template validation
Posted by Guillaume Polet <gu...@gmail.com>.
not sure it is much help here but:
There are two Eclipse plugin that validates the templates directly:
http://code.google.com/p/veloeclipse/
http://veloedit.sourceforge.net/
Otherwise you can write your own Java class to parse the template. If
recall correctly, this is not too complex to do and the velocity parser
should give you more details onto what is not right.
Cheers,
Guillaume
Le 28/01/2012 03:21, Steve Cohen a écrit :
> I would like to validate a template standalone.
>
> I have a template that is giving me errors and since there is a
> non-trivial build-deploy cycle to get it to run in my application I
> would like a way to validate the template file itself at the command
> line.
>
> I have found this:
>
> http://code.google.com/p/velocity-validator/
> but it appears to be non-functional. When run as directed it exits
> immediately telling me to supply a good log4j configuration. I try to
> supply one (but even this seems excessive for a standalone tool) to no
> avail.
>
> What is best way forward here?
>
>
> ---------------------------------------------------------------------
> 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