RE: Re: Sharing a pre-existing project

Hi,

What I often do is checkout all related projects using TortoiseSVN, then import the projects into Eclipse/WSAD, then use Team|Share to inform Subclipse that those projects are under SVN version control.

When doing this, Subclipse sees that the project already contains .svn directories (Same as the CVS plugin does for CVS directories!) and offers to validate the existing connection to the server.

It always works for me, but when recently tried it on a collegues computer there were exceptions and the exception itself couldn't be created b/c of trying to use a JDK1.4 exception constructor.

Does the procedure make sense?

(It doesn't make sense to me to put the projects on a shared network drive. But other than that it's often the way I work too.)

greetings,

--Tim

-----Original Message-----
From: McClain Looney [mailto:m@loonsoft.com]
Sent: donderdag 8 juli 2004 21:16
To: users@subclipse.tigris.org
Subject: Re: Sharing a pre-existing project

On Thursday 08 July 2004 01:52 pm, Matt Cristantello wrote:
> Here's what I'm trying to do:
>
> 1. Create a project and import it into subversion (outside eclipse,
> we're actually running a migration script from VSS to subversion).
> 2. Check out the files in the project to a shared network location.
> 3. Set up eclipse to use the shared network location as the project file
> directory.
> 4. Set up eclipse to share the project in the shared location into
> subversion for use in doing updates, commits, etc.

this sounds completely out of whack to me.

-- 
McClain Looney
LoonSoft LLC
m@loonsoft.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org