On Sun, Apr 13, 2008 at 6:57 PM, Lukas Rössler <luke_roessler_at_gmx.at> wrote:
> When i check out a repository which contains an eclipse project folder with
> e.g. rapidsvn and then open the project in eclipse it deletes all the '.svn'
> folders in subfolders of my 'bin' folder.
>
> I have e.g. the following folders:
>
> -repository_root
> |
> -project
> |
> - bin
> |
> - package1
> |
> - package2
> |
> - src
> |
> - package1
> |
> - package2
>
> (written as paths:
> repository_root/project/bin/package1/package2
> repository_root/project/src/package1/package2
> )
>
> each of the eight folders originally containing a .svn folder.
>
> repository_root/project is an eclipse project folder (containing a .project
> and a .classpath file). when i now open this project in eclipse the .svn
> folders in project/bin/package1 and project/bin/package1/package2 disappear.
> therefore i cannot update my working copy anymore (neither using subclipse
> nor via rapidsvn)
>
> I figured out you can solve the problem if you backup the bin folder, then
> open the project in eclipse and then copy the bin folder back to its
> original location.
This is not a Subclipse bug, it is the behavior of the Eclipse
builders when it does a rebuild all. The best thing is to just not
version these folders. You could perhaps configure Eclipse to build
to a different folder as another workaround. I am sure there are
issues filed for this at Eclipse but it seems unlikely they intend to
fix it. That said, I wonder why they are able to behave correctly
when you mix your compiled output in with your source folders. So it
might be worth raising it again.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-04-14 01:15:18 CEST