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

Re: Problems sharing existing project - naming and read-only

From: Antranig Basman <antranig_at_caret.cam.ac.uk>
Date: 2005-04-01 12:36:38 CEST

Mark Phippard wrote:
> Antranig Basman <antranig@caret.cam.ac.uk> wrote on 03/31/2005 10:42:30
> AM:

> If your project is already a Subversion WC, then when you do Share Project
> it should prompt you to associate it with the repository as opposed to
> walking you through the wizard pages you are seeing. For this to work,
> the project folder itself has to be part of the WC, not just some
> sub-folders.

Mark - thanks for the reply. No, the project is not currently under
version control. The code in question had been previously under CVS
control, before Jakarta-commons moved over to SVN. I have blasted the
CVS directories and now would like to reassociate the code with the
new repository, and be advised of any differences between its
current state and the head version before I update it. From what
I can see, there is no way to get this to happen with the current
version of Subclipse, as a result of the strange asymmetry between
what happens when you "Share project..." and what happens when you
check out a project as fresh, in particular the requirement for a
module name.
What *should* be possible (as with Eclipse CVS support) is even
creating a completely empty project, trying "Share Project..."
associating it with a repository location and then bringing it
up to date. Currently I don't see how this is possible.
Received on Fri Apr 1 20:36:38 2005

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