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
- A user workspace based one is in progress, see
Note that for now only the default one is included in the marketplace package.