Great thanks. The generated source looks correct.
Cheers Greg
On 27 April 2017 at 14:44, Claude Brisson wrote:
> Glad to hear it's a feature, not a bug...
>
> Almost all methods. org.apache.velocity.util.StringUtils now only
> contains several variants of the formatFileString() method, which s
Glad to hear it's a feature, not a bug...
Almost all methods. org.apache.velocity.util.StringUtils now only
contains several variants of the formatFileString() method, which should
not be used by Texe.
On 27/04/2017 14:40, Greg Huber wrote:
Claude,
I think I have managed to resolve it. Mos
Claude,
I think I have managed to resolve it. Most of the methods in
org.apache.velocity.util.StringUtils have been removed. Which texen relies
on for parsing the vm files via the context.
I updated the texen.properties variable to use the commons StringUtils
instead.
ie
#context.objects.strin
Thanks.
The old release candidate builds are available from the development
distribution svn history.
You can get the revision for a specific RC with:
svn log
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0
and then, you would typically download a specific RC with:
Well, I found a version dated 16th November 2016, which does work so its
not my setup.
Will try and debug the ant process for any errors.
On 14 April 2017 at 11:41, Claude Brisson wrote:
> A new test build of Velocity Engine 2.0 is available (RC8).
>
> No determination as to the quality ('alpha
I have noticed now that my bespoke taxen generator does not produce any
output. Also there are no errors generated.
Is it possible to back to previous snapshots (rc1) to see if the problem
exists?
There seems to be only the lasted release in the repo.
https://repository.apache.org/content/repos
