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

Re: Possible bug when Sharing a Project and using an existing module name

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-08-17 02:30:25 CEST

Gino Filicetti <gino@filicetti.net> wrote on 08/16/2005 05:34:44 PM:

> If I have an existing project and I want to hook it up to the same
> project in a repository (ie: if I am changing URLs or using a
> different repository location or username/pw combo), I end up with a
> StringIndexOutOfBounds exception with this stack trace:

I have good news and bad news. The good news is that I fixed this problem
recently and it will be in the next release (this problem has always
existed in Subclipse). The bad news is that it is not fixed the way most
people will want. The Subversion libraries do not currently have any way
to do what needs to be done here (turn an existing project into a valid
working copy). So all I could do to fix this problem is head it off in
the UI and make it clear you cannot do what you are trying to do.

See: http://subclipse.tigris.org/issues/show_bug.cgi?id=345

> This feature is very important to the way our development works. We
> have a large workspace that is mostly static and does not reside in
> the repository. This entire workspace is shipped to each developer,
> who then Connects only certain specific projects to the repository.
> If there is a workaround, I'd love to know.

The only workaround would be to ship a workspace where everything is
already a valid working copy. Then when the user does Team -> Share
Project Subclipse would just recognize it and offer to connect it to the

> Also, this is broken in the Subclipe plugin for Eclipse 2.x, the error
> there is:

That version of Subclipse has not seen any development in 18+ months.

Finally, there has been some discussion and even a proposed patch, to
enhance the Subversion checkout API to provide what was needed. In the
current form, the checkout would still download all of the files, but it
would just slip them under the current files to make it into a valid
working copy. There has also been some talk of adding rsync like
functionality so that only the changed files were downloaded. It wouldn't
hurt to post your requirements to the Subversion mailing list. Search the
dev@ list subjects for "takeover" to find the thread. I would suggest
taking Subclipse out of the equation. Just say you have a large code base
and you need to have a way for developers to turn select parts of it into
a working copy. I am sure the suggestion will be to just send them a
working copy to start, but at least you can register the requirement.
There has been some discussion as to how widespread the need is here.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Wed Aug 17 10:30:25 2005

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.