O.k. thanks, I'll keep an eye on those, but its no great hardship
managing SVN via tortoise at the moment :)
Thanks for the great product when users are not vandalising it :)
Regards
Nigel.
Mark Phippard wrote:
> On 10/1/07, Nigel Kane <nigel@kaneit.net> wrote:
>
>> No smoke pouring out of my monitor, but getting close to smoke pouring
>> out of my head.
>>
>> I have the following tree
>>
>> /root
>> /root/gfx
>> ...
>> /root/index.php
>> /root/.project
>>
>> I have an svn:ignore set in /root for "deploy"
>>
>> I have checked out another SVN project into /root/deploy and subversion
>> is fine with the integrity of the the file system.
>>
>> When I initially attach to the project (/root) all is fine and the
>> icons are as expected (little repository files and directories)
>>
>> Doing an update at the top level wipes the icon on the /root/deploy
>> folder and stops me from updating anything in that folder with its
>> repository though eclipse.
>>
>> Chances are I can do what I need to with branches, but a few things
>> limit me here, one of which being my potential lack of knowledge, but
>> the big one is that I don't want to be switching between branches and
>> merging things into HEAD all the time... in my instance, the deploy
>> directory is always a separate product from the root software (which is
>> a public product), but the 2 products come together on our servers
>> (including the developers laptop) internally.
>>
>> Is this a bug in subclipse? I'm pretty sure it is since the svn tools
>> and command line stuff work fine on linux, and tortoise doesn't seem to
>> have a problem in windows either?
>>
>
> Yes this is a limitation of Subclipse. Assuming I understand what you
> mean. If both of these:
>
> /root
> /root/deploy
>
> Are loaded into your Eclipse workspace as Projects then Subclipse does
> not handle that. We get in some kind of recursive update of the
> status of the files. This is because /root/deploy is also essentially
> under the /root project.
>
> http://subclipse.tigris.org/issues/show_bug.cgi?id=511
>
> Note that issue is RESOLVED, but there were two issue spun off it that
> still apply.
>
> You should be able to have the /root/deploy project disconnected from
> Subclipse, and then manage it via its existence in the /root project.
>
>
Received on Tue Oct 2 01:26:54 2007