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

Nick Faiz commented on DIREVE-242:
----------------------------------

Hi,

Well, I think this is a separate issue but agree with you about standardizing 
on versions of dependencies.

A clean-up is probably the way to go. I guess we should just create issues 
whenever we need to upgrade a dependency. 

The project structure of Apache Directory Server is complex, with quite a few 
project.xml files, so this sort of version confusion will occur. Perhaps we 
could simply maintain a wiki page which listed current dependencies or have a 
maven goal which checks different versions?

Nick

> 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

Reply via email to