On Thu, May 28, 2015 at 9:13 AM, Jacob Champlin <jac...@rentec.com> wrote: > So building 2.0 has not gone well. There are no valid instructions online, > eventually I figured out: > > $ svn checkout http://svn.apache.org/repos/asf/velocity/engine/trunk > velocity-master > $ cd velocity-master > $ mvn > > However, almost all the velocity-core test cases fail, which does not > inspire confidence. > > So now we are left with a choice. Wade knee deep in trying to clean all > this up, in which I wouldn't do half the stuff Velocity does... > > 1) I would drop maven > 2) I would go to 1 single distributable jar > > So basically fork velocity or go to change 10 years of code to Freemarker. > Fun.
You are not alone. I had the same concerns in April of 2014, and I also have 10 years of very complicated templates to deal with. Worse, it's also not possible to build later Velocity 1.x versions, such as 1.6, either. Especially the grammar, wherein lies a serious compatibility issue with 1.3.1 versions. It was frustrating enough that I gave up due to a personal lack of time and feedback from previous developers on how things worked. For now, I continue to press on with Velocity 1.3.1. I think the only thing that will prevent Velocity from going to the attic is for some of us to jump in and possibly revert some of the design decisions that prevent ongoing development. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
