I too use Velocity and find it quite stable. I've also extended it (as have most) with specialized tools, and as a result, it does precisely what I want it to do. I agree that it's important to take a look at the bug processing and make sure it is robust. But I don't understand your comment about losing ground in comparision to other engines. What does that mean in terms of being able to do things with other alternatives that you can't do with Velocity?
Regards, Terry ----- Original Message ----- From: "xMySign for Velocity" <[EMAIL PROTECTED]> To: "Velocity Developers List" <[EMAIL PROTECTED]> Sent: Monday, March 03, 2003 3:46 AM Subject: AW: AW: velocity 1.3.1 final? > Is there something in particular which is preventing you from using > the stable or development branches of Velocity? I'm using Velocity and it is quite stable, but it really lost ground in comparison with other template engines, and - that's the most important thing - there are quite a few bugs reported (have a look at the archives) and no one is fixing them, or - even worse - someone fixed it, but no one reviewed the patch so the bug is still left in the code. IMHO that's not the right way to find some interested commiters. I really would like to hear something about the thoughts of the current committers. what should be the future of Velocity? How we can find a lead? mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
