Probably because no one has felt motivated to upgrade and there's
likely some backward-incompatibilities. For Cayenne, someone would
need to install the new library, then test all of the default
templates to be sure that they still worked.
Considering that I'm pretty sure there have been some behavior changes
in Velocity 1.5, there's not much incentive to upgrade for those of us
making extensive use of personal velocity templates since we'd have to
go back in and retest our vast personal libraries of templates to be
sure they didn't change the generated code in some subtle way.
I'm not saying it shouldn't be done, only that there's a bit of work
involved in doing it. If it's going to be done, it probably should
be done sooner rather than later before Cayenne 3.0 users create a
large set of older-velocity-based templates.
On 9/4/07, Demetrios Kyriakis <demetrios.kyriaki..ooglemail.com> wrote:
>
> Hi,
>
> Are there any technical resons why not the latest Velcity version (1.5) is
> used by Cayenne (3.0)?
> It looks like it's stable, it's in the maven repository, has fixed many
> bugs, etc.
>
> Thank you,
>
> Demetrios.
> --
> View this message in context: http://www.nabble.com/Wny-not-velocity-1.5--tf4377048.html#a12476153
> Sent from the Cayenne - Dev mailing list archive at Nabble.com.
>
>
This archive was generated by hypermail 2.0.0 : Tue Sep 04 2007 - 11:11:34 EDT