2. (for reasons given in a previous mail) i'd prefer it if this goes into a branch rather than the head.
3. i'd prefer a service release for downstream developers to solve any possible problems with commons-collections before looking at logging. logging is a very delicate problem. it's crucial that it's quick, simple and robust.
4. i'd want to be certain that it'd work with tomcat before any changes to logging went into head.
- robert
On 11 May 2004, at 08:17, 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
