Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Please find attached a project.xml which upgrades nlog4j to 1.2.17 .

      It belongs in apacheds/trunk/project.xml

      1. project.xml
        5 kB
        Nick Faiz

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        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

        Show
        Emmanuel Lecharny added a comment - 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
        Hide
        Nick Faiz added a comment -

        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

        Show
        Nick Faiz added a comment - 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
        Hide
        Emmanuel Lecharny added a comment -

        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"

        Show
        Emmanuel Lecharny added a comment - 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"
        Hide
        Emmanuel Lecharny added a comment -

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

        Show
        Emmanuel Lecharny added a comment - sed s/ I'm the one who will /I'm NOT the one who will /
        Hide
        Alex Karasulu added a comment -

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

        Show
        Alex Karasulu added a comment - Nice Ceki just got the jar up to ibiblio now. Let's upgrade!
        Hide
        Alex Karasulu added a comment -

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

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

        Show
        Alex Karasulu added a comment - Updated all POMs using NLog4J in commit on revision 280455 here: http://svn.apache.org/viewcvs.cgi?view=rev&rev=280455
        Hide
        Emmanuel Lecharny added a comment -

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

        Show
        Emmanuel Lecharny added a comment - Closing all issues created in 2005 and before which are marked resolved

          People

          • Assignee:
            Alex Karasulu
            Reporter:
            Nick Faiz
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development