Hello Jochen, James,
As I have indicated previously, I am all in facot of maintaining the log taglib code
in the taglib project. However, I am worried about versioning problems between the
version of log taglib that log4j might be distributing with respect to the version
maintained at taglibs. Having to distinct copies of the same software seems like
asking for trouble.
Regards, Ceki
At 23:36 16.07.2001 +0200, [EMAIL PROTECTED] wrote:
>Hi James,
>
>sorry for the confusing list of emails, I am just answering all my
>emails, and started at the end.
>
>I agree with your proposal, make taglibs the source of development, and
>extend log4j for a "complete" distribution including taglib support for
>JSP development.
>
>Ceki, do you agree ? I would be happy with it.
>
>Bye, Jochen
>
>
>James Strachan schrieb:
>> Hi Ceki
>>
>> From: "Ceki G�lc�" <[EMAIL PROTECTED]>
>> > If I understand correctly,
>> http://www.adjacency.org/logtags.jsp is
>> > no longer pertinent...
>>
>> Yes, thats Joe's original taglib. The log taglib at
>> jakarta-taglibs
>> supercedes that one.
>>
>> > Whatever you deem most appropriate is fine with me.
>> IMHO,
>> > pre-packaging log taglib in log4j will give the former
>> a serious
>> > boost. This may seem like a silly marketing detail but
>> it can make
>> > a real difference for the log taglib. Regards, Ceki
>>
>> In terms of CVS repository and so forth I'd prefer the
>> log taglib to stay in
>> the jakarta-taglibs project.
>>
>> Though there's nothing to stop the log4j distribution
>> bundling the log4j
>> taglib inside it. e.g. the daily or release build of
>> log4j could cvs
>> checkout the log4j taglib and include it in the log4j
>> distribution.
>>
>> Then everyones happy, log4j comes with a taglib and the
>> log taglib
>> developers stay part of the jakarta-taglib project and
>> community..
>>
>> James
>>
--
Ceki G�lc� - http://qos.ch
