Hi Richard,
> a) It would be nice to keep the core log4j package as small and
> efficient as possible.
Within reason.
> b) Allow sandbox classes to be built into independant jars (for
> instance, if all I need is core log4j and the smtp appender, then I'd
> deploye log4j.jar and log4j-smtp.jar w
age-
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 6:40 AM
> To: Log4J Developers List
> Subject: Re: log4j-sandbox options
>
>
>
> Hi Ceki,
>
> That sounds fine. I must have forgotten about this resolution.
>
> Sorry for the bo
I'm thinking that:
a) It would be nice to keep the core log4j package as small and
efficient as possible.
b) Allow sandbox classes to be built into independant jars (for
instance, if all I need is core log4j and the smtp appender, then I'd
deploye log4j.jar and log4j-smtp.jar with my app).
The be
OTECTED]]
>> Sent: Tuesday, February 04, 2003 6:40 AM
>> To: Log4J Developers List
>> Subject: Re: log4j-sandbox options
>>
>>
>>
>> Hi Ceki,
>>
>> That sounds fine. I must have forgotten about this resolution.
>>
>> Sorry
But, does this mean that the selectors should be packaged in their own jar,
separate from the log4j-sandbox jar?
-Mark
> -Original Message-
> From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 6:40 AM
> To: Log4J Developers List
> Subject: Re
Hi Ceki,
That sounds fine. I must have forgotten about this resolution.
Sorry for the bother.
Jake
At 03:34 PM 2/4/2003 +0100, you wrote:
Hi Jake,
I thought we had this covered... It would fine to have
log4j.jar+selector.jar available to the shared class loader. This way
log4j+selectors
Hi Jake,
I thought we had this covered... It would fine to have
log4j.jar+selector.jar available to the shared class loader. This way
log4j+selectors would be accessible to Servlet Container class laoder and
the web-application class loaders. This results in one copy of
log4j.jar+selector.ja
One comment I have is that the servlet stuff needs to be run under
WEB-INF/lib of a webapp whereas the selectors need to be wherever an
existing log4j.jar is because there is two-way communication between the
selector and log4j proper. This is especially true for the
ContextClassLoaderSelecto
I think we should discuss some options for the log4j-sandbox:
1) Are there any other items we want to move from the core log4j cvs into
the log4j-sandbox cvs? Classes from the varia package? Move the
contributor directories?
2) Should the log4j-sandbox packages be released independently of the
