In 3.7.0, we released the tree-browsing feature. This article describes a couple of known quirks with the tree view and describes how to temporarily revert to the old browse feature if you run into trouble.
Rebuilding the browse tree
The browse tree is an indexed view of the underlying data. As a result, it’s possible for it to get out of sync and need a rebuild. To do this, create a new Rebuild repository browse tree scheduled task for the affected repository and run it once. This task is run automatically the first time you start the server after upgrading to 3.7.0.
NOTE: This task will take up to an hour for a repository containing three million assets, and you will be unable to browse the repository while it is running, so only run it when needed.
Slow tree browsing performance
Nexus Repository 3.7 introduces Content Selector Expression Language (CSEL), a new query language for content selectors. When you upgrade, it automatically migrates as many of your old JEXL content selectors to the new format as possible. However, some selectors cannot be upgraded automatically.
If you notice slow tree browsing performance, this may be due to JEXL content selectors that could not be migrated. Go to Admin → Repositories → Content Selectors and see if this is the case.
Known auth issue on Mozilla Firefox
On Firefox, authenticated users may get an authentication dialog each time they click the tree. The workaround is to either save your credentials or hide the dialog. We’ve filed a bug with Mozilla and they’re looking into it.
Turning off the browse tree
If the browse tree does not function properly, you can turn it off with a feature flag. Add nexus.browse.component.tree.enabled=false to your nexus.properties file, and restart the server. This will cause the UI to revert to the old flat list browse views.
NOTE: This feature flag will be removed in a future release, so turning off the browse tree is only a temporary fix. Please file an issue for any problem you encounter, so we can fix it.