You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Nick Faiz (JIRA)" <di...@incubator.apache.org> on 2005/09/04 14:43:30 UTC

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

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
 Assigned to: Alex Karasulu 
    Priority: Trivial


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


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

Posted by "Nick Faiz (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-242?page=all ]

Nick Faiz updated DIREVE-242:
-----------------------------

    Attachment: project.xml

> 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


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

Posted by "Nick Faiz (JIRA)" <di...@incubator.apache.org>.
    [ 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


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

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/DIREVE-242?page=comments#action_12322616 ] 

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

The wiki page already exist - even if it's not very easy to find :
http://wiki.apache.org/directory/IdeHome (look at "Committer special")

It may be better to write a maven task to do that, but I'm the one who will write it ! ("there are 10 kind of people : those who understand Maven, and those who don't" ;) 

> 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


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

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/DIREVE-242?page=comments#action_12322617 ] 

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

sed s/ I'm the one who will /I'm *NOT* the one who will /

> 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


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

Posted by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org>.
    [ 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


[jira] Closed: (DIRSERVER-475) upgrade to nlog4j.1.2.17

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-475.
---------------------------------------


Closing all issues created in 2005 and before which are marked resolved

> upgrade to nlog4j.1.2.17
> ------------------------
>
>                 Key: DIRSERVER-475
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-475
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Nick Faiz
>         Assigned To: 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-242?page=all ]

Alex Karasulu updated DIREVE-242:
---------------------------------

    Fix Version: 0.9.3

Nice Ceki just got the jar up to ibiblio now.  Let's upgrade!

> 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
>      Fix For: 0.9.3
>  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


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

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/DIREVE-242?page=all ]
     
Alex Karasulu resolved DIREVE-242:
----------------------------------

    Resolution: Fixed

Updated all POMs using NLog4J in commit on revision 280455 here:

http://svn.apache.org/viewcvs.cgi?view=rev&rev=280455

> 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
>      Fix For: 0.9.3
>  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