Just backported 1.2.16 changes to the extras companion. I haven't had any chances to extras on gcj or harmony, so might have some minor changes come from that. Will have to pick it up tomorrow.
Have we done OSGi metadata for any of the companions? mvn rat:check on extras will flag a lot of the comparison files. Should be excluded from the check, but I think the Apache RAT plugin doesn't honor exclusions, so may have to revert to the earlier codehaus. Maybe it is time to file bug reports for the releases that we want to make. If there are release blocking bugs, they should be listed as blockers for the release bug. I haven't checked the bug list, but I don't know of any. Was there a companion that we wanted to abandon? On May 14, 2010, at 11:49 PM, Scott Deboy wrote: > I think I'm in the home stretch of the features I'd like to get in to this > Chainsaw release, so I have cycles to help get companions out the door if > needed. > > Anything I can help with? > > Scott > > On Tue, May 4, 2010 at 7:16 PM, Curt Arnold <carn...@apache.org> wrote: > Need to back port some of the later fixes in the log4j 1.2.16 release back > into the extras companion. Other than that I don't know of anything. > > I've got some evenings free later this week and was going to try to clean up > some post 1.2.16 issues. > > > On May 4, 2010, at 12:04 AM, Scott Deboy wrote: > > > Are there any outstanding issues preventing us from moving forward with a > > release of the companions? > > > > Scott > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-dev-h...@logging.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
