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 deprecated API, fine for all, but I'd prefer to wait for a > stable release of Log4J before modifying MX4J's build. What you need to do is to change your codebase to use the newer Level and Logger instead of Priority and Category, which has been around since 1.2.0. Log4J mistakenly also removed the RootCategory and replaced with a RootLevel, but there were no interim 'deprecated' period, so after Avalon was affected by the change the RootCategory was re-introduced in their codebase. So, 1. You change your codebase. 2. If you release, you can build and release against/together with Log4J 1.2.8 3. Such release will also work with Log4J 'next release'. 4. Such change will make Gump happy :o) Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
