[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] SVN repository view

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-05-05 16:22:24 CEST

On 5/5/07, Thomas Hallgren <thomas@tada.se> wrote:
> Hi,
> I have a question regarding how Subclipse connects projects to
> repositories. My problem is that I get a new repository entry although I
> already have one that ought to match.
>
> Background:
> The Buckminster plugin uses the ISVNClientAdapter to do most tasks. We
> obtain it from an ISVNRepositoryLocation when we find one that is
> appropriate (i.e. has a root that matches our desired root) among the
> known repositories. We no match is found, we use the SVNProviderPlugin
> to create a new instance.
>
> We do this because we want to be able to read individual files in the
> remote repository without checking them out, and when we finally check
> something out, we don't want it to be bound to the workspace. The
> binding stage takes place later on.
>
> Problem:
> I start Eclipse on an empty workspace. I go in to the SVN Repository
> Exploring and create a new entry:
>
> svn+ssh://dev.eclipse.org/svnroot/technology/org.eclipse.buckminster
>
> When I look at the properties for that entry, it lists the "Repository
> url" as stated and the "Repository root url" as:
>
> svn+ssh://dev.eclipse.org/svnroot/technology
>
> Looks OK. After that, I start a Buckminster materialization. I verify
> (using the debugger) that it finds the repository in question and use
> the ISVNClientAdapter it obtained from it when the checkouts are made.
>
> The checkout ends with a loop where Buckminster binds everything to the
> Eclipse workspace (i.e. it creates the projects). Somehow, Subclipse is
> notified of this and maps the projects to a SVN repository. My problem
> is that Subclipse now decides to create yet another repository location
> where the "Repository url" is exactly the same as the "Repository root url".
>
> How can I prevent that the new repository location is created? I want
> the projects attached to the location that is there already.

Generally if a match is found it will use it. It does the match based
on the location you entered though, not the root. In general, I would
recommend you define the root as the location, but if the Eclipse
repository is going to put multiple projects in the same repository,
you might not want to do that.

You will probably need to debug the code to see what it is doing and
why it is not matching.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Sat May 5 16:22:35 2007

This is an archived mail posted to the Subclipse Dev mailing list.