On Fri, 2005-09-23 at 14:50 +0200, jerome lacoste wrote: > On 9/23/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: > > On Fri, 2005-09-23 at 10:36 +0700, Kev Jackson wrote: > > > Hi, > > > > > > I've been looking at the use of commons logging in exec. Coming from > > > ant dev, it would be nice to refactor ant to use the commons-exec > > > package, but Ant has it's own logging mechanism (using logging > > > listeners), and I'm pretty sure that the ant code base will not change > > > to using commons-logging throughout except as the listener, and as far > > > as I'm aware the ant team want to keep the ant bootstrap as minimal as > > > possible (require nothing but an xml parser and a jdk). [1] > > > > > > There's also the problem of the minimum version of Java supported by > > > commons-exec, though this looks like it will be less of a problem. > > > > I'm concerned about this issue too and have been looking into ways to > > automate the testing to make sure that we're not using any JDK1.3+ API > > parts. Do you have any good ideas? > > I can also set up an automated build that uses 1.3... that should > catch errors (a little bit late, but easy to set up).
That would be useful too, but I was hoping for something that would break the build if you where to start using JDK1.3+ stuff Note that not using JDK1.3+ means that you'd have to run the tests with java 1.2. -- Trygve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
