Yeah, I just realized I was using an out-of-date ant. Switching to 1.7 reveals a few incompatibilities in our build files that I will need to clean up.
I like the idea of versioning the jars. It seems the ones that I am updating are already distributed that way (with their version in the filename). I think you just volunteered yourself to be a reviewer of this change! :) On 2010-01-21, at 11:51, David Nault wrote: > Shouldn't be a problem for Webtop. Might as well upgrade all the way to Ant > 1.7.1. I'm looking forward to the fix for this issue: > > https://issues.apache.org/bugzilla/show_bug.cgi?id=37386 > > When you add the new jars it would be great if their version numbers were > included in the file names. > > David > > > On Wed, 20 Jan 2010, P T Withington <[email protected]> wrote: > >> Date: Wed, 20 Jan 2010 20:45:13 -0500 >> From: P T Withington <[email protected]> >> Subject: [Laszlo-dev] Upgrading some of our build tools >> To: OpenLaszlo Developers <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=us-ascii >> >> I have a nifty solution for http://jira.openlaszlo.org/jira/browse/LPP-8503 >> but it depends on updating our ant, rhino, and bsf versions and adding >> commons-logging to our ant/lib/ jars. >> >> I need to run: >> >> Apache Ant version 1.6.5 >> Rhino 1.7 release 2 >> >> and update bsf.jar to 2.4.0, which requires adding commons-logging.jar 1.1.1 >> >> Is this going to be a problem for developers? >> >> In theory these are all fairly stable publicly available tools, so there >> should not be an issue with updating our dependencies, but I thought I >> should check before I do. >
