Re: JXTA logging framework

As there have been no objections to this move we have begun planning to 
make the transition from Log4J to java.util.logging. The current plan is 
to convert the platform, cms and shell projects immediately following 
the upcoming 2.3.8 code freeze (May 22nd).

The conversion will be implemented following the code freeze so as not 
to impact other changes which will be pushing hard to complete before 
the code freeze.

We ask that all committers refrain from committing changes to platform, 
cms and shell projects on May 23rd until the (massive) update is committed.

Mike

Mohamed Abdelaziz wrote:
> 
> Community members,
> 
> We are considering a change to the logging framework for the upcoming 
> release (June 2006) of the JXTA JSE platform and supporting projects 
> (shell, CMS). This would replace Log4J with java.util.logging, and would 
> remove one of the required jars and ease the deployment of the platform 
> in embedded applications.  This change should have no impact on other 
> project which rely on Log4J.  The planned changes would also include a 
> logging object allowing for runtime and static logging configuration 
> (including the ability to omit logging through compilation)
> 
> We would like to solicit your input as to whether this change would have 
> any negative impact upon your application or development process. We are 
> also interested in hearing suggestions and comments to improve JXTA 
> logging and/or lessen the impact of this change.
> 
> 
> The JXTA Team
> 
> The change would be along the following lines :
> 
> import org.apache.log4j.Level;
> import org.apache.log4j.Logger;
> ..
> ..
> if (LOG.isEnabledFor(Level.INFO)) {
>      LOG.info("Now connected to JXTA network");
> }
> 
> 
> Becomes  :
> 
> 
> import java.util.logging.Level;
> import java.util.logging.Logger;
> import net.jxta.Logging;
> ..
> ..
> if (Logging.INFO && LOG.isLoggable(Level.INFO||)){
>      LOG.info("Now connected to JXTA network");
> }
>