Nexus plugin 2.0.1 release notes

This release notes provides the release highlights and bug fixes of Nexus 2.0.1 plugin.

Name of the plugin: CTF-Nexus-Integration-Plugin-2.0.1.

Note: You must upgrade to latest Nexus plugin version regardless of whichever TeamForge version you have installed or upgraded. To upgrade to latest Nexus version, check this page: Upgrade the TeamForge-Nexus integration plugin .

Release highlights of Nexus 2.0.1 plugin

Minor patch release.
Enhanced the TeamForge top navigation bar supported by Angular JS.
Available from TeamForge 16.7 release.

Known Limitations with TeamForge-Nexus integration

Here's a list of known limitations of TeamForge-Nexus integration.

While it is possible for users (all TeamForge users but site administrators) with 'create repository' permission to create binary repositories via the TeamForge Binaries application, such users cannot create repositories directly on the Nexus server (using the Nexus UI) as there is no TeamForge project mapping available in Nexus.
A TeamForge user cannot be configured as an anonymous user in Nexus as TeamForge users are not available in the Nexus database.
TeamForge broadcast messages and license notifications are not visible in Sonatype Nexus pages in TeamForge. This is due to a limitation with the TeamForge-Nexus integration plugin.
When the TeamForge Project administrator changes the existing binary permissions for a user, the changes will not immediately take place due to the cache implementation in Nexus to improve the performance of session handling. Due to this limitation, when a user tries to create a new Nexus repository, he will get the permission denied error. Hence the user must wait for the changes to take effect. However, the user can view the changes immediately on a standalone Nexus application by restarting his session on it.