commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Graham <>
Subject Re: [beanutils] remove dependency on commons-logging
Date Tue, 11 May 2004 12:53:37 GMT
I was reluctantly in favor of copying certain Collections classes as a
temporary solution to removing that dependency but I don't see why we want
to permanently copy Logging classes to other projects.  Commons Logging is
an abstraction for Log4j and java.util.logging; now we're going to add yet
another abstraction above Commons Logging?  That doesn't make any sense to

I'm not a BeanUtils committer but as a user and Commons committer here's
my -1.


--- Simon Kitching <> wrote:
> Hi,
> As no-one shot down my proposal as posted earlier, here is a proposed
> patch to beanutils to make commons-logging a completely optional
> dependency.
> The Log class is a copy of o.a.c.l.Log, and is intended to be committed
> to the beanutils cvs tree as o.a.c.l.Log.
> The LogSource class is intended to be added in o.a.c.beanutils.
> logging.patch changes all calls to LogFactory.getLog into calls on
> LogSource.getLog.
> The build.xml.patch removes commons-logging from the buildfile, as after
> this patch it is neither a compile-time nor a runtime dependency. 
> I'm expecting comments (maybe screams :-). The only *possible* concern I
> am aware of about this patch is where multiple libs containing copies of
> o.a.c.l.Log are used and they have different security policies applied. 
> Cheers,
> Simon
> > ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message