Mark Phippard wrote:
>> I'm not using external source directories. Entire Eclipse project
>>directory is outside of workspace dir, so I can logically share same
>>project between multiple workspaces. Eclipse's .project and .classpath
>>files reside in the root of that external project directory. When you
>>create new project Eclipse's project wizard will create these files in
>>the directory you choose and it is also trying to guess for the source
>>directories, so I just delete anything wizard would add. This hasn't
>>been much different since Eclipse 2.0 or even earlier.
>>
>>
>I started down that path but didn't complete the wizard because it seemed
>like it was going to delete my folder. In my case, I had a complete
>Eclipse project already in the target. It sounds like maybe you just have
>the source when you start? I can try that.
>
>
It looks like Eclipse or Subclipse is cahing something. so, I had to
delete project from workspace (without deleting directory) after
disconnect. When I deleted all .svn folders (manually or by choosing to
delete on disconnect) and imported project back I can't share it back to
the same repository anymore.
>>I'll try that, but it is not quite related to the issue I have.
>>
>>
>The only real difference seems to be whether the external folders start off
>as an Eclipse project or not. If one method can work and the other can't
>....
>
>
I tried import and it does not work here. However I noticed that
commandline svn client set read-only attribute for all .svn/* files
(subclipse didn't do that) on windows. When I removed read-only flad and
deleted created/imported this project back into workspace wizard finally
started to see .svn files!
regards,
Eugene
Received on Fri Jan 7 21:34:34 2005