This question is in reference to Atlassian Documentation: Searching FishEye
Fisheye displays file paths relative to a repository name. For example, if I have a repository named PhobosTrunk that is mapped to the SVN path /mars/moons/phobos/trunk, and someone has checked in a file in the phobos project: src/main/java/org/sky/observer/orbital/MoonShadow.java, the path to this file is displayed in Fisheye as PhobosTrunk/src/main/java/org/sky/observer/orbital/MoonShadow.java.
Any developer that needs to check out the phobos project to make changes needs to know the full SVN path (including /mars/moons/phobos/trunk), but instead only sees "PhobosTrunk/...".
How can a (non-admin) user discover the SVN path defined for a repository for the purpose of using it in SVN commands?
This isn't an answer, but rather a heads-up on another issue that you may stub your toe on. We had a repository that we were accessing (via Tortoise and Fisheye) as https://collab1/svn/repo1/project1. We added svnserve to work around a bug in the https interface, and could access it (via Tortoise) as svn://collab1/svn/repo1/project1. But that URI didn't work in Fisheye. Finally we figured out we had to use svn://collab1/svn/project1. It seems that "repo1" wasn't, in fact, a repository name, but rather a "location" name?! And the repository name was "project1". I still don't quite understand, but the moral is that when going from one way of accessing SVN to another, you may have to play with the URIs in rather mysterious ways.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs