This page last changed on Jul 23, 2009 by smaddox.

This page contains additional information that you may find useful when setting up your FishEye server for the Atlassian Connector for Eclipse. You will find the step-by-step instructions in Configuring the Eclipse Connector.

On this page:

Background to the FishEye Configuration and Mappings

As an Eclipse plugin, the Atlassian connector needs additional configuration for the following reasons:

  • The connector needs to know which FishEye server is serving the selected source file, and in which FishEye repository the file exists.
  • The connector needs to know the current revision (or version) of the local file, in order to take the user to the proper place in the history on the FishEye server.
  • Moreover files may come from various places in the repository, such as trunk, branches, tags, modules for CVS, etc.
  • FishEye and Eclipse may use different access protocols to access the same source. For example, FishEye may use file:// for SVN, while Eclipse uses https://.
  • As a developer, you may have many projects open in a single Eclipse workspace. These projects come from different source repositories (SVN,CVS, etc) that are potentially indexed by different FishEye servers.

It would be time-consuming and unnecessary to configure FishEye for each project, because often many projects come from the same repository and are served by single FishEye instance and maybe by one or two FishEye repositories in that instance.

The solution:

  • Configure the FishEye mappings not per project but per SCM setup (path) used locally by the project.
  • Combine the selected SCM path (as seen locally in Eclipse) with the FishEye server (as configured in the Mylyn task repositories) and the FishEye repository from the selected FishEye server.
  • Given a source file, the Atlassian Connector for Eclipse checks the SCM path from which the file was checked out, and finds the appropriate mapping (the combination as defined above). Then it knows which FishEye server and which FishEye repository the selected file belongs to.

Limitations

Please take note of the following:

  • The configuration does not keep track of re-configuration in the Mylyn task repositories. If the mapped FishEye server is removed from the list of task repositories, your FishEye functionality may stop working.
  • The file may be deleted on the server side or FishEye may be out of sync with the SCM repository, so you may get an HTTP 404 error.
  • Please refer to the notes on support for specific source control repositories.
RELATED TOPICS

Configuring the Eclipse Connector
IDE Connector Documentation

Document generated by Confluence on Mar 17, 2010 21:17