There will likely be a forthcoming message indicating that
logging-log4j failed which will have failed 200+ projects due to
dependency. This was due to an unfortunate removal of jakarta-oro as a
dependency for log4j. While I was adding Gump projects for the
optional jars needed for Chainsaw,
On Feb 26, 2005, at 5:25 PM, Jacob Kjome wrote:
Curt, I understand your wanting to keep compatibility. I tend to
agree that if we can do it at the same time as adding new features,
then we should strive for that. We broke compatibility with
RepositorySelector's, but because there are few (i
OK, every take a deep breath and count to ten. Please keep one thing in
mind. Everyone is acting in what they feel are the best interests of the
project. Ceki is making changes he thinks are important. Curt is
registering concern and reverting changes to keep things in sync. Everyone
is vo
Ok, guys, don't you think all this has gotten a bit out of hand?
Ceki, apparently you committed code that cause incompatibilities with those
implementing appenders against Log4j-1.2. There was no discussion of this
beforehand and no one, but maybe Curt (because of the phone call), had a
clue a
Ceki,
I would have thought making changes to such a core interface with
potential backward compatability issues may have started with a
discussion. We don't know what the usefulness of the changes are
because you haven't told us. It's highly likely that once you've told
us your plan, we will
carnold 2005/02/26 12:51:49
Modified:.build.xml ugli.xml
Log:
Parameterized names of optional jars, fixed jar metadata
Revision ChangesPath
1.151 +15 -8 logging-log4j/build.xml
Index: build.xml
===
On Feb 26, 2005, at 1:21 AM, Scott Deboy wrote:
log4j-core jar doesn't have the socket classes. the log4j-optional
jar needs added to the classpath.
also need log4j-oro and log4j-xml in the classpath as well.
Thanks for the help, Curt
Currently, the "logging-log4j" project only calls the "log4j.
On Feb 26, 2005, at 11:51 AM, Ceki Gülcü wrote:
Mark,
Over the years, I have always strived to listen to all the opinions
voiced. I also try to accommodate opinions diverging from mine and
when it boils down to a matter of taste, I tend to privilege the
opinions of others over my own. Certainly,
People,
I can't get work done without having it reverted a few days later.
I don't recall other incidences. In this case, a set of changes was
brought to our attention as causing Hivemind project to fail and I
think it justified reverting the changes until we analyzed the
situation. I did give
On Feb 26, 2005, at 10:00 AM, Ceki Gülcü wrote:
Curt, today there is not a single appender which implements the
Appender interface without extending the AppenderSkeleton class.
All we know for sure is the code in the Gump universe. The Appender
interface is complex enough that it would drive al
Mark,
Over the years, I have always strived to listen to all the opinions voiced.
I also try to accommodate opinions diverging from mine and when it boils
down to a matter of taste, I tend to privilege the opinions of others over
my own. Certainly, there are examples that go both ways.
From a m
Hello Ceki,
Well, I'm not a committer, so experience tells me you'll completely ignore
my input and pretend as if it had never been voiced.
Nevertheless, as one of those poor schmucks who maintains an Appender
outside of the log4j base, I do have an opinion about this debate, and it's
certainly n
At 12:01 AM 2/26/2005, Curt Arnold wrote:
On Feb 25, 2005, at 3:22 PM, Ceki Gülcü wrote:
At 09:48 PM 2/25/2005, Curt Arnold wrote:
I can't stress how strongly that I believe these changes are bad and
will unnecessarily cause some users of 1.2 to stay with log4j 1.2 or
encounter broken behavior du
At 02:19 AM 2/26/2005, Curt Arnold wrote:
On Feb 25, 2005, at 6:57 PM, Paul Smith wrote:
Appender the interface is the contract for all Appenders,
AppenderSkeleton just happens to provide some decent plumbing and support
in an effort to make it easy to write a custom appender.
Anywhere within lo
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-chainsaw has an issue affecting its community integration.
This iss
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project logging-log4j-tests has an issue affecting its community integration.
This issue
16 matches
Mail list logo
