Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-14038

Group repositories created through the Provisioning API do not preserve member order

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.0
    • Fix Version/s: 3.6.0
    • Component/s: Repository, Scripting
    • Labels:
      None
    • Story Points:
      1
    • Release Note:
      Yes
    • Sprint:
      Core Sprint 102

      Description

      Two problems introduced by the fix for NEXUS-13064:

      • Jackson serializes LinkedHashSet to a HashSet when transmitting to the client, losing the ordering
      • Orientdb serializes LinkedHashSet to OTrackedSet when converting the mapped attributes on a Repository configuration, so even though the member order is initially correct with the in-memory representation, restarting the server will reload from the db and therefore lose the order

      NOTE:

      • for the small number of Repositories that are likely affected by this, the manual remediation after this fix is to load the Group repo in the UI, reorder the members as desired and save; from this point forward the order should be consistent

        Attachments

          Activity

            People

            Assignee:
            KWright Kristofer Wright
            Reporter:
            krobinson Kelly Robinson
            Last Updated By:
            Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title