commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <>
Subject Re: [logging][PROPOSAL] a solution to incompatibility between log4j versions
Date Wed, 19 May 2004 17:08:01 GMT
> On the log4j we are making a very serious effort to keep everyone
> happy.

And that is greatly appreciated. :)

I really wish you weren't having to go through this, I can hardly imagine
how frustrating it must be to maintain an old interface for two years,
attempting a clean deprecation, only run into such a gotcha. I do feel for
you, and think users appreciate anything you can do to help.

> Tell us specifically what fails and we will do our best to fix
> it. Rolling back everything is not specific enough.

Then can I say, whatever "changed in the public API"? ;-) Seriously though,
I'd mentioned them previous in thread. That said, this thread has morphed,
moved over 4 list, etc, so here again:

Best I can tell from here:

These two are the Priority deprecation:

You already reverted this one, thanks (it was RootCategory, I think):

Again, these are only the ones I can tell from within Apacge/Gump. External
users who've not moved from Priority, are probably the same.

> Moreover, we have provided very clear set of instructions that safely
> address the c-l compilation problems. I think log4j is the wrong tree
> to bark at.
> I noticed that
> <>bootstrap-ant no longer
> builds. Is it a related problem?

Hmm, good question. Seems possible, but odd that it works here:

(although here it assumes no log4j).

The check does look for :

    <available property="log4j.present"

Did that change?

I'll ask a Gumpmeister (who has access to that box) to take a closer look,
and get back to you.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message