I fully agree with Geir's response. Using velocity is simple and
straightforward. Logs are good. Bugs normally have been minor,
could be fixed with a patch or using a simple workaround. All on
this list have contributed greatly in getting it ready for release.
Now that its a release, I can really recomend it for a production
environment. Some of you will find some bugs or quirks, but Geir
is an ace in getting them fixed. Patches to fix bugs or inconsitencies
from everyone else are also very welcome.
The Vel-lists have calmed down a lot in the last days, so things
seem to be working fine! Some new users poped in, and I believe
there is a growing community just using it, happy, and silent!
(Or was this due to ApacheCon? But no storm after the calm has
arisen ;)
The parser has been Geir's fiance (I guess theres one person not
wholly happy about this), so we have reported bugs to him instead
of patching. Since the Vel syntax is (now) really simple, I guess
a cleanup uverhaul could solve this and other hidden bugs (are
there somewhere good examples for writing/using javacc?).
At this moment Velocity is in the stage of real world (production)
environment testing. Any problems are fixed quickly and everyone
is happy with it. Some new requirements.proposals are being
evaluated and may find their way into one of the next releases.
Velocity has a good test-bed to avoid breaking current functionality.
Note that the real world will show some new quirks that need to
be fixed and will then be covered by the test-cases. This is the
best way to improve a production release (which initially is prone
to contain some buggies).
Cheers,
:) Christoph
"Geir Magnusson Jr." wrote:
>
> Rafal Krzewski wrote:
> >
> > jeff wrote:
> >
> > > I just did some testing with latest from CVS and discovered the
> > > following problems
> > >
> > > 1) The basic $$ problem: (I have mentioned this before)
> > <snip>
> > > 2) The ${ problem:
> > <snipp>
> > > 3) The disappearing } problem:
> >
> > Gee, isnt't this demotivating that released Velocity still has problems
> > like that? I remember that that long time ago someone said that quality
> > of the parser is going to be the greatest advantage of Velocity over
> > WebMacro....
>
> I'm not sure how demotivating it is. Doesn't bother me at all from the
> user point of view, given the number of hoops I had to jump through in
> WebMacro when I still used it, and how pleasant and nice I find Vel to
> use in my day to day work life. People might want to chime in here
> though.
Chimed above loud and clear!
>
> It bothers the heck out of me as a Velocity committer though, and will
> have the fix in ASAP.
>
> > I guess I still don't use Veloctiy in production environment for a
> > reason.
>
> What reason, and what do you use?
>
> If you are being honest about your sentiments, you can't use WebMacro
> either, because they can't even seem to decide on their syntax... they
> just added a new parser and are deprecating their old one. Enjoy.
>
> > Rafal
> >
> > PS. I really appreciate your hard work Geir, but the parser bug parade
> > seems to be going on forever...
>
> You hve a very good point, but there is a major rewrite I want to do to
> resolve this and related problems in the parser, and wanted to wait
> until after the release 1.0, as the syntax and parser is stable, modulo
> this issue.
>
> geir
>
> --
> Geir Magnusson Jr. [EMAIL PROTECTED]
> Developing for the web? See http://jakarta.apache.org/velocity/
