rombert / ereviewboard

A mylyn-based Eclipse integration for Review Board
46 stars 31 forks source link

Create review auto selects the wrong svn repository - can't diff in eclipse #121

Open stevetarver opened 11 years ago

stevetarver commented 11 years ago

Our ReviewBoard installation has http, https, and local svn repository connections

Behavior: When creating a new review request, eReviewBoard always selects the last in that list: the only one I can't use: localhost.

Problems: I cannot double click the files in the Mylyn task and view them in the Eclipse differ. Get svn: PROPFIND of '/svnlocal/trunk/.../file.java': 405 Method Not Allowed (http://localhost)

I cannot apply the diff in a review request to my Eclipse work space - getting a "Could not find a matching project for the resources in the review request" error dialog.

Environment: Replicated on Mac and Windows 7. Using Eclipse Juno 4.2.1 and the latest build of eReviewBoard. I originally used http://a.b.c/svn as the sole subclipse repository in my workspace. I created a new workspace using only https://a.b.c/svn hopping the auto selection would distinguish it from the others - did not work.

Can't find a way to select the proper svn repo through configuration, etc. I have tried turning off public visibility and Publicly accessible on the ReviewBoard svn repo configuration I don't want to use, creating new Eclipse workspaces and reconfiguring the Mylyn repo each time to no avail. I have also tried different query configurations hoping that would change the auto-select behavior - also did not help.

Suggest: If there are multiple svn repos in the ReviewBoard config, let the use select one in the create review request dialog.

Really nice plugin and idea, btw. Thanks for your efforts.

rombert commented 11 years ago

Thanks for the report - and thanks for the kind words.

I've added some troubleshooting instructions at https://github.com/rombert/ereviewboard/wiki/Troubleshooting . Can you please activate the org.review_board.ereviewboard.subclipse.ui/debug trace and attach the logs? If they are sensitive you can mask the actual URLs .