shibboleth-dev - RE: Logging library plans
Subject: Shibboleth Developers
List archive
- From: "Wu, Albert" <>
- To: <>
- Subject: RE: Logging library plans
- Date: Wed, 18 Jul 2007 15:47:39 -0700
> The main purpose of the fork is to stamp the thing 1.0 and
> rename it, so that it won't interfere with the "real" log4cpp
> anymore. In doing this, I will probably need to make some
> changes to allow for either my version or some potential
> future version of log4cpp that actually works to be used.
>
> I'd note that both versions of the SP (1.3 and 2.0) are going
> to be modified, as they will be sharing the same library set
> going forward.
>
> Are there any concerns about this?
>
Licensing aside, my main concern would be that this forked version of
log4cxx use the same configuarion file syntax as current version of
Log4J. Well, at least it should be a strict subset if you don't intend
to implement all features current Log4J supports. Since most of us
likely need to configure Log4J elsewhere, it'd be much, much nicer to
have the same config file syntax...
albert wu
UCLA AIS
Middleware Infrastructure
- Logging library plans, Scott Cantor, 07/18/2007
- Re: Logging library plans, Michael R. Gettes, 07/18/2007
- RE: Logging library plans, Scott Cantor, 07/18/2007
- Re: Logging library plans, Michael R. Gettes, 07/18/2007
- RE: Logging library plans, Scott Cantor, 07/18/2007
- Re: Logging library plans, Ian Young, 07/18/2007
- Re: Logging library plans, Scott Cantor, 07/18/2007
- RE: Logging library plans, Wu, Albert, 07/18/2007
- Re: Logging library plans, Scott Cantor, 07/18/2007
- Re: Logging library plans, Michael R. Gettes, 07/18/2007
Archive powered by MHonArc 2.6.16.