And please document it somewhere.
On Fri, 2002-06-07 at 15:42, Nicola Ken Barozzi wrote:
From: Andrew C. Oliver [EMAIL PROTECTED]
going to commons loggin when set.
-1 - Ditch commons logging. Lets just do System.out. I'm tried of
fighting with library dependencies and having
And make sure it doesn't load commons logging classes unless explicitly told
to.
-- Glen
And please document it somewhere.
On Fri, 2002-06-07 at 15:42, Nicola Ken Barozzi wrote:
From: Andrew C. Oliver [EMAIL PROTECTED]
going to commons loggin when set.
-1 - Ditch commons
When I debug, I use the graphical chainsaw to see the logs.
It's quite cool IMHO.
If we default to noop when a property is set, we don't even need commons
logging, since only our factory and logger know of it's existence, so it
can
safely be removed.
Deal?
Are you saying going
From: Glen Stampoultzis [EMAIL PROTECTED]
When I debug, I use the graphical chainsaw to see the logs.
It's quite cool IMHO.
If we default to noop when a property is set, we don't even need commons
logging, since only our factory and logger know of it's existence, so it
can
safely
Are you saying going straight to log4j again (when prop is set)?
NO, straight to System.out when the prop is set. Log4J was a nightmere!
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail:
From: Andrew C. Oliver [EMAIL PROTECTED]
going to commons loggin when set.
-1 - Ditch commons logging. Lets just do System.out. I'm tried of
fighting with library dependencies and having
no clue how to turn logging on because its not documented ANYWHERE that
I can see (I always muddle
From: Glen Stampoultzis [EMAIL PROTECTED]
Amazingly the logging still seems to produce problems for our users. It's
really quite amazing how a simple thing such as logging can cause so many
problems.
I am thinking perhaps we should simply be getting rid of logging from our
application. I
3. Only load commons logging if a system property is setup.
+1
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
We are still using the wrappers ;-)
The fact is that they use commons logging underneath.
I think that simply giving a -Dpoi.logging=enable check system would
remove
the problem.
Probably, but I wonder whether we really need the dependency at all. I've
personally never even used the
From: Glen Stampoultzis [EMAIL PROTECTED]
We are still using the wrappers ;-)
The fact is that they use commons logging underneath.
I think that simply giving a -Dpoi.logging=enable check system would
remove
the problem.
Probably, but I wonder whether we really need the dependency
Amazingly the logging still seems to produce problems for our users. It's
really quite amazing how a simple thing such as logging can cause so many
problems.
I am thinking perhaps we should simply be getting rid of logging from our
application. I can see these potential options:
1. Comment
11 matches
Mail list logo
