You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2005/09/04 15:00:30 UTC

[jira] Commented: (DIREVE-242) upgrade to nlog4j.1.2.17

    [ http://issues.apache.org/jira/browse/DIREVE-242?page=comments#action_12322613 ] 

Emmanuel Lecharny commented on DIREVE-242:
------------------------------------------

Hi,

just a question about jars in general: we have many different versions of jars all over the projects (like commons-collections-3.0 and common-collections-3.1)

What about a big cleanup combined with the packaging of one of the next release (0.9.3, 0.9.4, ...) ?

It's not urgent, though, but it tickles my neo-con convictions about good coding practices ;)

> upgrade to nlog4j.1.2.17
> ------------------------
>
>          Key: DIREVE-242
>          URL: http://issues.apache.org/jira/browse/DIREVE-242
>      Project: Directory Server
>         Type: Improvement
>   Components: server main
>     Reporter: Nick Faiz
>     Assignee: Alex Karasulu
>     Priority: Trivial
>  Attachments: project.xml
>
> Please find attached a project.xml which upgrades nlog4j to 1.2.17 .
> It belongs in apacheds/trunk/project.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira