db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Becke <be...@u.washington.edu>
Subject Re: [OJB] Issue #OJB220 - Log4j jar is required at runtime even if not used.
Date Fri, 05 Dec 2003 19:42:09 GMT
I can't figure out how to attach a patch to an existing issue in Scarab, 
so here it is instead.  This patch just moves all of the Log4j code into 
  Log4jLoggerImpl.

Thanks,

Mike



Michael Becke wrote:
> You can view the issue detail at the following URL:
> 
>     http://nagoya.apache.org/scarab/issues/id/OJB220
> 
> Type
>  Patch
> 
> Issue ID
>  OJB220 (Log4j jar is required at runtime even if not used.)
> 
> Reported by
>  Michael Becke
>  becke@u.washington.edu (becke@u.washington.edu)
> 
> New issue details:
> ---------------------------------------------------------
> 
> Summary set to "Log4j jar is required at runti..."
> Description set to "LoggerFactoryImpl requires Log..."
> Operating system set to "All"
> Issue created
> Platform set to "All"
> 
> ---------------------------------------------------------
> This message is automatically generated by the Scarab
> issue tracking system.  For more information:
> http://scarab.tigris.org/
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
> 

Mime
View raw message