That seems to be the case actually. So that answers that question.
It does get a bit weirder. If I do the delete, the directories show
up. Then I do an "override and update" command. The package comes back
in the project, but the _svn packages still stick around in the project
tree. And they stay there even if I do a refresh command on the
project. I have to restart my eclipse client for it to clear up.
Mark Phippard wrote:
> On 8/1/07, Andy Adamczak <firstname.lastname@example.org> wrote:
>> There is an evironment flag available called SVN_ASP_DOT_NET_HACK that
>> the svn client libraries look for. If it's set to any value, the
>> directory that the svn client libraries use is changed from .svn to
>> _svn. This also seems to work fine for most operations in the subclipse
>> plugin. The problem is that if you delete a java package through
>> eclipse, the _svn directories do not get removed, and then eclipse
>> thinks there are 5 new empty packages with weird names (for example if
>> you delete a package called x.y.z, you then get the packages x.y.z._svn,
>> x.y.z._svn.prop-base, x.y.z._svn.props, x.y.z._svn.text-base, and
>> x.y.z._svn.tmp in the project.
>> Is this a subclipse issue or an eclipse issue? Someone is not handling
>> the deletion case correctly. The folder x/y/z stays on disk, along with
>> the _svn directories.
>> The work around is close your workspace and manually go do the package
>> directory you tried to delete it and actually delete it. Then restart
>> eclipse. You have to do that every time you delete a package. Is this
>> a known issue, and if not, should I file it with the Eclipse project or
>> Subclipse project?
> It sounds like you are just not doing commit after the delete. When
> you delete a folder in Subversion it is only marked for deletion. It
> does not go away until you actually commit it.
Received on Wed Aug 1 22:46:50 2007