On 05/28/2015 10:02 AM, Antonio Petrelli wrote:
2015-05-28 15:57 GMT+02:00 Jacob Champlin <jac...@rentec.com>:
On 05/28/2015 09:44 AM, Mike Kienenberger wrote:
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.
Funny thing is 10 years ago, I had the choice between Freemarker and
Velocity. I went with
Velocity because it was an Apache backed project, and I assumed it had
more developers maintaining it. So it was
software from an established open source house, vs some guys pet project.
So I agree that "some of us should jump in" and try to save this.
However, this is not what I should be working on right now. I am sure
everyone else is in the same boat, which is how it got to be this way.
Please don't complain, but maintain. You can fork it in Github, participate
with patches, you can even publish your fork (changing its name).
I was working for Velocity some years ago, remember that most of us are not
paid by anyone to do this work, we are all volunteers. Apache projects are
not made "by professionals", although someone invests money on them, but
it's not always this way.
Antonio
I agree, that is what open source is all about. Just easier said than done.
-Jacob
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
