I don't know if it's valid, but the current trunk of the log taglib uses commons-logging [so it can sit on top of log4j, jdk logging etc]. It seemed like a good idea N years ago [best intentions and all], but it can be rolled back if it's problematic.
I'm quite happy to mentor someone if they want to work on the log taglib. :) Hen On 2/18/07, Gaurav Arora <[EMAIL PROTECTED]> wrote:
The project I am working on may need to use the taglib. I will definitely try my best to patch it and send the patch on the list. I was thinking of patching the benchmark taglib as well to use a variable instead of printing the time. I haven't contributed to the ASF projects(mainly because I come from the scripting world) before so I was wondering if there is a process that needs to be followed. Should patches and such be discussed with other developers on the dev mailing list first? Thanks, Gaurav On Sun, 18 Feb 2007 15:48:19 +0100, Martin van den Bemt <[EMAIL PROTECTED]> wrote: > I don't think anyone is currently working on that.. > We are always interested in patches however :) > > Mvgr, > Martin > > [EMAIL PROTECTED] wrote: >> I was wondering if there was an updated Log taglib available somewhere. > The one >> which is up for download on the official site is quite old because it > still >> uses the old Log and category classes. Is it still being worked on > actively? >> >> Gaurav Arora >> >> >> --------------------------------------------------------------------- >> 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] --------------------------------------------------------------------- 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]
