lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Engels" <reng...@ix.netcom.com>
Subject RE: Lucene and Java 1.5
Date Tue, 30 May 2006 21:45:31 GMT
Log4j can be configured to use delegate to the standard 1.5 logging. In fact
this is preferred so you have STANDARDIZED logging support (and not a
different logger for every library).

All NEW code should use the 1.5 logging for simplicity of configuration and
for future ease of integration. 

-----Original Message-----
From: Doug Cutting [mailto:cutting@apache.org] 
Sent: Tuesday, May 30, 2006 3:54 PM
To: java-dev@lucene.apache.org
Subject: Re: Lucene and Java 1.5

Robert Engels wrote:
> 1.5 has built in Logging support - eliminating the need for Jakarta
logging.

Logging was first added in Java 1.4.

> That is like saying Jarkarta Collections does not use JDK 1.5. No one 
> that develops NEW software uses Jakarta Collections - they use the 
> Collections support in the JDK.

But lots of folks do use log4j in favor of Java's built-in logging. 
Commons Logging permits one to code to a generic logging API and let the
application configuration determine whether that's Java's logging, log4j or
something else.

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message