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

Re: [Subclipse-users] SVN Repository locations creation using Project Set

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 15 Sep 2008 14:42:13 -0400

On Mon, Sep 15, 2008 at 2:30 PM, Acheson, Douglas
<douglas.acheson_at_rbc.com> wrote:

> I have noticed a strange (well strange to me) behaviour with Subclipse
> when using Project Sets. I have create a project set file (.psf) that
> references all my projects I need to work on. When I import the psf file
> SVN repo locations are created. This is goodness, but what is strange is
> the repo location is. The repo location is from the repo level, i.e.
> highest possible node in the tree, not what is specificed in the project set
> file. Here is an example (the names and locations have been changed to
> protect the innocent):
>
> <?xml version="1.0" encoding="UTF-8"?>
> <psf version="2.0">
> <provider id="org.tigris.subversion.subclipse.core.svnnature">
> <project reference="0.9.3,http://scm/svn/aa/bb/cc/trunk"/>
> </provider>
> </psf>
>
> Repo location created in RAD/Eclipse is http://scm/svn/aa
> Expected to see http://scm/svn/aa/bb/cc or http://scm/svn/aa/bb/cc/trunk
>
> Why is this the case, and how can it be changed?

Yes, we go out of our way to add the location using the repository
root URL. If, for example, we add the trunk URL, then you cannot
navigate to the branches/tags area in the UI. What if you want to
switch to working on a branch. The other issue would be if you were
importing 10 projects from the same repository we would create just 1
location instead of 10.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-09-15 20:43:00 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.