Re: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)

2004-05-25 Thread Adam R. B. Jack
> >From time to time we get an email similar to this one, and we try to promptly fix the build. Thanks, that is aprpeciated, so mind if automate that? This entry will do it. > I am in a busy period now, but I'll try to get the build going as soon as I can, running against the latest stable

Re: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)

2004-05-25 Thread Niclas Hedhman
On Tuesday 25 May 2004 15:23, Bordet, Simone wrote: > The only thing I'd prefer to avoid is to make our build running against the > latest CVS (which are usually unstable), since this is gump's job. You should build and release against the latest stable Log4J, no doubt. > If Log4J removed deprec

RE: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)

2004-05-25 Thread Bordet, Simone
Hi Adam, > I don't know if you are aware of Apache Gump, but it is a > continuous integration tool. See: > >http://gump.apache.org Yes, we know gump. >From time to time we get an email similar to this one, and we try to promptly fix the >build. Last time was Axis (they reintroduced the A