Known limitations with TeamForge-Nexus/Artifactory integrations

Here is a list of known limitations of TeamForge-Nexus integration.

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.
TeamForge-Artifactory integration
Artifactory repository names must be unique. You cannot have two or more repositories with the same name even if the repositories are of different types such as Remote or Hosted repositories. However, if you want to create two (or more) repositories with like-sounding names, you can devise and follow a repo naming convention to uniquely identify repositories of different types. For example, a "central" repo can be named as "central-local" and "central-remote" to uniquely refer to the "Hosted" and "Remote" repository types respectively.