Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-11148

Allow choice of Nuxeo Drive hierarchy configuration

    XMLWordPrintable

    Details

    • Type: User story
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.6.0-HF26, 5.8
    • Component/s: Nuxeo Drive
    • Backlog priority:
      960
    • Upgrade notes:
      Hide

      Removed FileSystemItemFactoryDescriptor#enabled

      Show
      Removed FileSystemItemFactoryDescriptor#enabled

      Description

      We need to find a way to chose a given hierarchy configuration among existing ones.
      Could be at build time with a Maven profile, or at runtime through an extension point, but that would mean embedding all the possible configurations in the marketplace package.
      For now we manage:

      • The default hierarchy ("Nuxeo Drive" virtual folder parent of all synchronization roots) in the nuxeo-drive-core module
      • A permission and user workspace based one in the nuxeo-drive-hierarchy-permission module, see NXP-11074
      • A user workspace based one is in progress, see NXP-10663

      Note that for now only the default one is included in the marketplace package.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 days Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days
                  3d

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.