> > Hello, > > > > With the possiblity of several new features on the plate, I suggest > > that consideration be given to rolling these together into a 2.0 > > release. The features might be (in no particular order): > > > > * Improved whitespace handling > > it's never clear that 'improved' is the right word. > 'different' is how > I think of it :)
I would see the mechanism of a filter better fitting this situation. Something like: #filter (whitespaces) VTL #end Configuration could be (in velocity.properties): filter = whitespaces, somethingelse whitespaces.filter.class = org.apache.velocity.runtime.filter.WhitespaceFilter ... It would be something like a BodyTag in JSP. > I don't think a 2.0 is warranted unless the float change is > significant > enough. I guess if it is, then indeed a 2.0 is right. Perhaps a 1.4 would be fine. Then all the stuff that is *not* breaking the backwards-compatibility along with some code-refactoring could be implemented to have a stable codebase to proceed to 2.0 adding the number support and filters :) and [fill in] then. 1.4.x should then only be maintained (removing severe bugs / security issues). I think more discussion on this is needed. > It's clear 1.3 is overdue. I'll release it ASAP and get the > patches in. Great! Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
