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

Re: Commit in synchronize view

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-01-06 20:55:48 CET

Eugene Kuleshov <eu@md.pp.ru> wrote on 01/06/2005 02:50:42 PM:

> Mark Phippard wrote:
>
> > > I can browse it in repositories view too. Can you try to checkout
> > > jsvn using command line svn client, then add that dir as a project
to
> > > Eclipse workspace and then try to share it?
> >
> > Why wouldn't I just check it out using Subclipse (which I have done
> > in the past). I do not understand how you checkout a project using
> > the command line and then see it in Eclipse anyway. Why would
> > Eclipse even know the project exists if you do not use the Eclipse UI
> > to create the project? You cannot, generally speaking, just create
> > stuff in your workspace and then use it in Eclipse. It ought to be
> > created by Eclipse.
>
> Well, there could be variety of reasons for that. For instance I could

> loose my workspace and have to recreate it from scratch (or, say I need
> to import existing project into a different workspace) and still have
> local uncommitted changes. With CVS I can create new project in Eclipse,

> point it to the existing source direcotry, attach and synchronize it
> with remote CVS repository. I see no reasons why it should not be
> possible with SVN.

It might be helpful if you had just started off by saying this. It sounds
like you are using the feature of Eclipse to have projects that are
located outside your workspace -- Linked Resources. There are numerous
reports of that not working. I was under the impression you got a message
to that effect somewhere though. I have never tried it.

> If you prefer this approach then I can suggest to checkout it with
> Subclipse, then disconnect it from SVN without deleting .svn directories

> and then try to connect it back. Technically it will be the same as
> checkout form command line and importing it into Eclipse, but if first
> case will work and second will not, then it will mean that Subclipse is
> not interoperable with command line svn or/and TortoiseSVN.

We interoperate fine with those tools. I regularly use them on the same
WC. The difference is that I originated my projects by checking out with
Subclipse so that all of the Eclipse linkage is established. This has
nothing to do with the WC, it is just what needs to be done inside Eclipse
so that Eclipse will call our code.

Also, I regularly disconnect and reconnect projects in my workspace. It
works great.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Jan 7 06:55:48 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.