Ian,
What Eclipse version you are using?
>Hi Eugene,
>
>[...]
>
>
>> 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.
>>
>>
>
>I do that quite a bit. It works fine for me. You _do_ have to be
>careful that the case of the path to the working copy matches what is
>stored on disk - the best way I've found to be certain of this is to use
>the browse when importing the project to pick the directory (or once
>I've typed the directory, browse and accept and that will correct any
>case inconsistencies). Once that's done, it's just a matter of
>Team->Share Project..., select SVN and it spots everything is already
>configured and offer to connect to the repository to check.
>
>Note: I don't use linked resources, just projects external to the
>Eclipse work area.
>
>Cheers,
>
>Ian Brockbank
>Applications Software Team Leader
>e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
>scd: ian@scottishdance.net
>t: +44 131 272 7145
>f: +44 131 272 7001
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
Received on Fri Jan 7 21:09:34 2005