Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v618)
In-Reply-To: <D1639D06CFBD014F87F3978DA7038B93DBDFD0@ns1017.SSSI.seagull.nl>
References: <D1639D06CFBD014F87F3978DA7038B93DBDFD0@ns1017.SSSI.seagull.nl>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <91B04ACC-C3C7-11D8-914C-003065DC754C@blueyonder.co.uk>
Content-Transfer-Encoding: 7bit
From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
Subject: Re: [logging] after 1.0.4: unfinished business
Date: Mon, 21 Jun 2004 22:11:31 +0100
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>


On 21 Jun 2004, at 21:47, Gary Gregory wrote:

> [snip]
>> memory log
>> ----------
>> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27663
>>
>> i quite like this idea but it's not really a major feature. i'm
>> inclined to try to keep the core jar small by creating another
> optional
>> jar called loggers containing loggers which are less likely to be
> used.
>> the distribution would contain both jars. maybe avalon log could be
>> moved there too.
> [snip]
>
> From our product's POV, I've always used CL as a thin wrapper to log4j
> with the remote possibility that we will switch to JDK 1.4 logging when
> we move from Java 1.3 to 1.4.
>
> I have no pb with useful stuff being the jar but it sounds like some of
> these are new features that are not in the "wrapper" dept, which argues
> to me for putting it in a separate jar.
>
> Then there are questions like: should the "memory log" really be in CL
> as opposed to logj4?

that's a good question :)

the binary distribution is now quite large (due to the improved, 
mavenized documentation). so, as long as the actual core jar stays 
small, i'm a lot happier adding new loggers to an optional jar if 
there's a good chance that people would find them useful but i'd be 
interested to hear other people's opinions on this one...

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org