Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <43028511.4080002@atlassian.com>
Date: Wed, 17 Aug 2005 10:30:09 +1000
From: Nick Faiz <nick@atlassian.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: notification of possible problem with nlog4j-1.2.14 &  log4j
 compatibility
References: <43016FE9.3000403@atlassian.com>
 <6.0.3.0.0.20050816215006.033d9900@torino>
In-Reply-To: <6.0.3.0.0.20050816215006.033d9900@torino>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Ceki,

As noted on the nlog4j-dev list I will upgrade our dependency and test 
ASAP.

Thanks for the quick response time. :)

Nick


Ceki G�lc� wrote:
> 
> Hello Nick,
> 
> The problem should be fixed in NLOG4J version 1.2.16. With this version 
> code compiled with log4j will run fine in both log4j and NLOG4J. I think 
> this is the problem you encountered and would like to see fixed. So, 
> that's done. :-)
> 
> However, the inverse is not true. Code compiled with NLOG4J will only 
> run with NLOG4J. This means that your code, when compiled with NLOG4J, 
> will depend on NLOG4J, which in my humble opinion is a rather reasonable 
> requirement. Especially if you consider that NLOG4J has SLF4J support 
> which log4j does not have.
> 
> At 06:47 AM 8/16/2005, Nick Faiz wrote:
> 
>> Guys,
>>
>> Here is notification of a possible incompatibility between log4j and 
>> nlog4j.
> 
> 


-- 
ATLASSIAN - http://www.atlassian.com/

Confluence - the enterprise wiki - tried it yet?
http://www.atlassian.com/confluence/
--