This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 231169

Summary:	Cannot authenticate with SVN when another project is open pointing to a different SVN Repository URL
Product:	versioncontrol	Reporter:	bdkosher
Component:	Subversion	Assignee:	Ondrej Vrabec <ovrabec>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	P3
Version:	7.3
Hardware:	PC
OS:	Windows 7
Issue Type:	DEFECT	Exception Reporter:

Description bdkosher 2013-06-12 17:57:01 UTC

I have two Subversion-housed Projects open at the same time; one has a repository root URL of https://somehost.com/svn/P1 and the other has a repository root URL of https://somehost.com/svn/P2. Both project's working copies are using the svn 1.7 format.

I am using "Javahl" as my preferred client with the path to the client libraries set to "C:\Program Files\SlikSvn\bin" where version 1.7.0-SlikSvn-1.7.0-X64 (SlikSvn/1.7.0) X64 is installed.

When I go to Tools->Options->Versioning->Subversion->Manage Connection Settings, I am only able to see the Repository URL of the first project I opened, https://somehost.com/svn/P1.

When I attempt to SVN Update the second project via Team->Subversion->Update, I am prompted with an "Authentication failed" dialog which shows project 1's Repository URL instead of project 2's. The Repository URL field is grayed out so I cannot change it. 

Ironically, when I attempt to view Versioning Info for project 2, I am prompted with the "Authentication failed" dialog, but am able to hit "Cancel" and see the Versioning Info dialog, which shows the correct Repository Root URL fro project 2.

I would like to be able to interact with both SVN repositories as I am working on both projects simultaneously. NetBeans should be able to recognize which SVN Respository URL corresponds to which project and only attempt to authenticate with that repository.

Comment 1 Ondrej Vrabec 2013-06-12 18:15:47 UTC


*** This bug has been marked as a duplicate of bug 228410 ***

Comment 2 bdkosher 2013-06-12 18:32:35 UTC

I have doubts this is the same issue as bug 228410. That bug says it was a regression introduced in 7.3.1. I am experiencing the problem in 7.3.

I will upgrade to 7.3.1, though, to see if the problem persists.

Comment 3 bdkosher 2013-06-12 22:02:51 UTC

Upgrading to 7.3.1 did resolve the issue.