On 6/29/07, Ahmed Mohombe <[EMAIL PROTECTED]> wrote:
Nathan Bubna-3 wrote: > > VelocityTools 2.0 is, in my estimation, ready for an alpha release. I > Why not user the same version number like Velocity?
never done it before. all Tools 1.x releases are (i believe compatible with all 1.3+ Engine releases).
This way it would be much simpler for the users to match versions. E.g. they would intuitively use Velcity 1.6 with VelocityTools 1.6.
it would be cool if that just happened. for Tools 1.1, 1.2, & 1.3, we were relatively lucky to have the Tools version numbers line up to the Struts 1.x version numbers, but that was 90% coincidence. i don't, however, think it is worth it to alter development pace (rushing or holding back on release cycles) just to keep numbers in sync. better to just document what version(s) of Velocity are required for each version of VelocityTools. Tools 2.0, while it is highly compatible with 1.x versions, is largely a rewrite of the internal infrastructure and involves a lot of package shuffling and refactoring. what compatibility there is comes through a huge number of deprecated classes and methods put/left in place just for that purpose. Those will start disappearing in subsequent version minor version releases. Calling this a 1.x release would be quite a stretch.
Ahmed. -- View this message in context: http://www.nabble.com/-VOTE--Release-VelocityTools-2.0-alpha1-tf3991455.html#a11361412 Sent from the Velocity - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
