Release highlights of Nexus 2.0 plugin

Usability of the Nexus installer (used to integrate Nexus with TeamForge) has been
enhanced.

Improved peformance while loading Nexus UI.

Bug fixes in Nexus 2.0 plugin

When users log on to Nexus using CTF user credentials, the Nexus UI showed poor
performance. This is fixed.

Fixed the time delay due to the presence of Nexus plugin in Maven builds.

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.