Henning, I'm holding off with my vote for the moment-- I've some minor concerns on the docs. Am I allowed to make the changes or since we are in the middle of a vote is it too late?
I'm worried about making sure existing users of 1.4 have a seamless upgrade experience. I drafted some text in the Wiki, but I think it's mostly superseded now. But we should add to the README.txt file something like: This release is a drop-in replacement for earlier versions of Velocity. No changes to your application should be required other than changes to the dependent jar files. Specific changes to the jar files include: * JDOM has been upgraded to 1.0 * Commons Collection has been upgraded to 3.1 * Commons Lang 2.1 has been added In addition, * Ant 1.6 or greater is required for building. * Java CC 3.2 or greater is now required for compiling parser files. * HSQLDB 1.7.1 is required for running unit tests. I worry about this, because when I tried last Fall to upgrade an app of mine to Velocity 1.5-beta, the commons collection upgrade was really a hassle. (due to a conflicting conflict with Torque 3.0 which requires an earlier version). We need to highlight this change. A minor issue: xdocs/docs/jar-dependencies.xml is inconsistent with xdocs/docs/build.xml. Specifically the list of dependencies is missing antlr and junit. best, WILL On 1/28/07, Henning Schmiedehausen <[EMAIL PROTECTED]> wrote:
On Sun, 2007-01-28 at 23:25 +0100, Henning Schmiedehausen wrote: > [X] +1 Yes. > [ ] 0 I still don't care. > [ ] -1 No, because ________________________________. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
