[unstandard] Ingesting the Log taglib

[Henri Yandell <fl...@gmail.com>]

I'm +1 to pulling the whole log taglib into Unstandard. My only
question is what we should put it on top of. Should we:

a) Go with the last release and use log4j.
b) Use the current trunk's approach and use commons-logging.
c) Give up the ghost and use the JDK logging.

I'm tempted by c), it's just easier.

Hen

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

Re: [unstandard] Ingesting the Log taglib

[Rahul Akolkar <ra...@gmail.com>]

On 7/23/07, Henri Yandell <fl...@gmail.com> wrote:
> I'm +1 to pulling the whole log taglib into Unstandard.
<snip/>

+1

> My only
> question is what we should put it on top of. Should we:
>
> a) Go with the last release and use log4j.
> b) Use the current trunk's approach and use commons-logging.
> c) Give up the ghost and use the JDK logging.
>
> I'm tempted by c), it's just easier.
>
<snap/>

I'd say (b), stick with trunk, its relevant ATM (though maybe not for too long).

-Rahul


> Hen
>

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