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
