Adam Hupp <email@example.com> wrote on 03/24/2006 01:29:06 PM:
> I'm trying to do a compare against a branch in Subclipse but it is not
> working how I would expect. My repository layout is like this:
> I go under the Team menu and choose "Configure Branch/Tags", and then
> add /branches/release-1.0 as a branch. If I compare file1 against this
> it uses this nonexistent path: /branches/release-1.0/file1 and fails.
> If I add /branches/release-1.0/project1 as a branch the compare works,
> but there are some problems. First, the branch name is "project1",
> which does not describe the branch. Second, this means I have to add
> the branches for every project, for every branch. With M projects and
> N branches that means I have add define M*N branches. In my case M is
> ~50 and N is ~7. That doesn't even count tags, which are even more
> I see that I can change my repository layout so that each project has
> it's own trunk and branches directory but that causes other problems.
> To branch each project I would have to branch them all individually
> instead of doing it once at the top level. There is an analagous
> problem when checking out.
> Is there something I'm missing here? If not, are there any plans to
> make this work in the future? What would be ideal for me is to define
> a relationship such that /branches/release-1.0 is known to be a branch
> /trunk, and then all files (in any project) under /trunk can look for
> a branch copy under /branches/release-1.0. If it exists, then show
> that branch in the compare dialog.
You have to set these properties on every project anyway so specifying the
extra bit in the path does not add anything and it allows us to correctly
transform the URL. As for the name, you are totally in control of what
name to specify, just override it to be release-1.0, or r1.0, whatever you
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Mar 24 19:40:55 2006