Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-39

Consider rebranding OpenDS -> OpenDJ in 3.0 tree

    XMLWordPrintable

Details

    • Task
    • Status: Done
    • Major
    • Resolution: Fixed
    • 2.6.0
    • 2.6.0
    • core apis
    • None

    Description

      We should consider doing a global search / replace of all occurrences of OpenDS and replacing them with OpenDJ in order to have clearer branding (including package names). Oracle does not seem to be maintaining OpenDS, so there seems no point in maintaining source compatibility for non-existing upstream changes. In addition, OpenDJ 3.0 will bring a significant refactoring of the core server and effectively fork OpenDS since we will not be able to easily back port our own fixes to out of date OpenDS code.

      Attachments

        Issue Links

          Activity

            People

              matthew Matthew Swift
              matthew Matthew Swift
              Matthew Swift Matthew Swift
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: