I did a large amount of work last year on the Velocity 1.7 branch, split
it into a main project and sub projects that integrated with other
components, updated the packages, switched to slf4j and got it building
under Maven. I am using it in an Android project I am trying to
finish. That has stalled for the moment as I am on contract. I posted
this on this list and everyone was supportive, but they wanted me to
look at the 2.0 branch and see if I could not lose those updates. I did
not know about the 2.0 codebase. I have not had time to try and merge
the changes. I would be more than happy to push my changes to github
and have anyone review them and determine if the changes I made would be
a good restarting point. I have always liked Velocity. And doesn't
IntelliJ still use it in their base framework for the templates?
Fred
On 05/28/2015 08:33 AM, Mike Kienenberger wrote:
On Thu, May 28, 2015 at 11:21 AM, Jacob Champlin <jac...@rentec.com> wrote:
On 05/28/2015 10:48 AM, Mike Kienenberger wrote:
I would like to point out that we are very happy running Velocity 1.7, in
fact there is not a single new feature we want. So we agree
its a stable mature product that doesn't need a lot of changes. Our problem
is the world around it has been changing, and Velocity isn't
keeping up. Apache Commons in particular. Looks like its easy to go to
latest lang, and digester, but collections is a different beast. So
velocity
isn't even keeping up with its dependencies from the same organization. Not
to mention I am sure the code could benefit from newer java features.
And I'm in the same boat.
I don't need velocity to evolve. I just need it to keep up and
remain backward-compatible so that it can continue to be used as other
software packages are upgraded.
I'm going to make time "soon" to try once again to work forward from
my 1.3.1 environment up the chain of releases to 1.7 while maintaining
backward compatibility. I'm far more interested in a 1.8 maintenance
release than a 2.0 release.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
