Hi Emmanuel,
Yes, I see your point now. Sorry, I had thought that nlog4j was only
listed as a dependency in the project.xml on the apacheds trunk.
After running a grep I can see that it is in ASN and in quite a few
places within standalone.
I had thought you were talking about versioning problems in general
when you added your comment previously to DIREVE-242.
Well, this problem is simply going to keep increasing, as you have
pointed out.
Do you agree with a maven goal that will scan the project structure
for dependency clashes? Any alternative ideas for controlling version
havoc?
Cheers,
Nick
On 06/09/2005, at 11:15 PM, Emmanuel Lecharny wrote:
Hi think I have more than looked at DIREVE-242 ...
My point is that we may upgrade to 1.2.17, without any problem, but we
lust do it for the whole project. As a new version is still to be
delivered really soon, it can be the perfect target.
Alex ?
On Tue, 2005-09-06 at 21:33 +1000, Nick Faiz wrote:
Hi,
Could someone please look over DIREVE242 to think about upgrading
nlog4j?
http://issues.apache.org/jira/browse/DIREVE-242
Hopefully it will get rid of the NoSuchMethodError I was seeing a
few weeks ago.
Cheers,
Nick
---------------------------------------------------------------------
------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-
virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.
