Hi,
I've installed the plugin as we would like to extend our use of MantisBT and track issues and their resolution.
The dev team is using SVN installed on a Windows VM via a Collabnet package (I wasn't there when it was installed, so I don't have much info about all of this) which includes ViewVC.
The "root" URL is a collection of repositories, and each "sub path" is a repository on its own with the traditional repository structure (trunk, branches, tag). For example, let's say the "root" URL is: http://my-server:8080/svn/. If I go to that URL (and fill the username + password), I get a webpage with the listing of all the repositories. I can then go to a specific repository http://my-server:8080/svn/my-project and check it out.
As far as I understood from the SourceSVN documentation, it is possible to manage this type of configuration.
I pointed the "root" URL in the "URL" field of the plugin as stated in the documentation, but I cannot import the whole thing. The plugin really quickly returns an error with an empty string:
APPLICATION ERROR #plugin_SourceViewVC_svn_cmd
Subversion execution returned an error: "".
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
I imagine that the issue is that the plugin cannot list the whole collection of repositories to parse each one individually. But I tried several different configurations of the plugin and cannot make it work:
- URL:
http://my-server:8080/svn/ or http://my-server:8080/svn (read somewhere the trailing slash could be an issue)
- ViewVC URL: filled or not, together with URL or with an empty URL
- ViewVC Root As URL Component Enabled?: checked or not
- Standard Repository: checked or not
If I enter, in the URL, directly the "sub-path" (http://my-server:8080/svn/my-project), it works, it pulls the change set and I can see the revisions (cannot have the "diff" to work, but that is not really an issue for our use case).
Am I not configuring it properly? Should I change something on the server side (which may not be an easy task as it's a company repository and if I fail doing so... let's say it's not going to be fun 😜).
Thanks in advance for your help!
Hi,
I've installed the plugin as we would like to extend our use of MantisBT and track issues and their resolution.
The dev team is using SVN installed on a Windows VM via a Collabnet package (I wasn't there when it was installed, so I don't have much info about all of this) which includes ViewVC.
The "root" URL is a collection of repositories, and each "sub path" is a repository on its own with the traditional repository structure (trunk, branches, tag). For example, let's say the "root" URL is:
http://my-server:8080/svn/. If I go to that URL (and fill the username + password), I get a webpage with the listing of all the repositories. I can then go to a specific repositoryhttp://my-server:8080/svn/my-projectand check it out.As far as I understood from the SourceSVN documentation, it is possible to manage this type of configuration.
I pointed the "root" URL in the "URL" field of the plugin as stated in the documentation, but I cannot import the whole thing. The plugin really quickly returns an error with an empty string:
I imagine that the issue is that the plugin cannot list the whole collection of repositories to parse each one individually. But I tried several different configurations of the plugin and cannot make it work:
http://my-server:8080/svn/orhttp://my-server:8080/svn(read somewhere the trailing slash could be an issue)If I enter, in the URL, directly the "sub-path" (
http://my-server:8080/svn/my-project), it works, it pulls the change set and I can see the revisions (cannot have the "diff" to work, but that is not really an issue for our use case).Am I not configuring it properly? Should I change something on the server side (which may not be an easy task as it's a company repository and if I fail doing so... let's say it's not going to be fun 😜).
Thanks in advance for your help!