Got it. I missed this was Velocity 2.0. Sounds great then. We should set an official targeted JDK.
For patches to the 1.x line, we should continue to support JDK 1.3 I think even though it's so old. There's no reason to ditch it. WILL On Thu, Jul 8, 2010 at 8:00 AM, Antonio Petrelli <[email protected] > wrote: > 2010/7/8 Will Glass-Husain <[email protected]>: > > Regarding your comments on oro, etc. One key thing is we need to > preserve > > backwards compatibility, at least for the 1.x line. What this means is > (a) > > no changes to key interfaces, and (b) must remain run-compatible with JDK > > 1.3. (though compiling requires JDK 1.4). Practically this means we > cannot > > use JDK 1.4 regular expression classes. > > Sorry? The 2.0 version number usually means that it is *incompatible* > to Velocity 1.x. > And, come one, Java 5 is at EOL since the last year: > http://java.sun.com/products/archive/eol.policy.html > And Java 1.3 isn't even mentioned. I think that, at least, a move to > Java 5 is necessary for the sake of everyone. > Otherwise, let's name it Velocity 1.8, not 2.0, it does not make any sense. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
