I've found in the more recent releases of Subclipse that it no longer adds a
new repository location when you check out a project.
> http://svn/repos/project would be the root url right?
Yes. Assuming you have: .../repos/trunk .../repos/branches .../repos/tags
I'm not sure I agree with the statement "since tags and branches are
organised that way". Branches and tags merely a (cheap) copy of section of
the repository. There's nothing that dictates you HAVE to have your tags
and branches under directories called tags and branches.
There are/were two suggestions in the redbook for repository layout:
So, right away we can't enforce a particular format or set the tool to
expect certain things.
And again, a branch and a tag is merely a copy of an existing direct and in
theory go wherever you want to put it, but logically it's easier to organise
them in the suggested ways.
From: Hugo Visser [mailto:firstname.lastname@example.org]
Sent: Tuesday, 15 February 2005 9:07 AM
Subject: Re: Newbie: Subclipse and repository layout
Greg Irvine wrote:
> The easiest solution is to select the "New Location" option when you share
> your project, and specify the full path to trunk (or the branch if you may
> be adding it to the branch).
The only downside of this approach is that I'll get a repository
location for each project. I have many fairly small projects in one
repository right now. Ofcourse I can set up a location for browsing
only. What would be the value for root url if I set up a project like
http://svn/repos/project/trunk. http://svn/repos/project would be the
root url right?
>>It would be a nice feature to have subclipse create the trunk, tags and
>>branches directories and automatically switch to trunk after you share a
>>new project. Maybe somekind of "project template" feature?
> I digress on this issue because the branches/tags/trunk is merely a
> recommendation. How users organise their repository is completely up to
> user and I don't think the tools should force users to use a layout that
> not be applicable to their situation.
I understand, but it's also something specific for SVN since tags and
branches are organised that way. When we were on CVS we didn't have to
worry about the "right" structure because there was no need for it. Just
create a module and off you go. Since I'm looking at the task to
introduce SVN as _the_ source control for our java projects I'd like to
have it as easy as possible :)
But I'll try to create separate locations in Eclipse. It sounds more
like the way it should be done :)
Thanks for the help.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Feb 15 09:31:21 2005