| Read-only notification in combination with subclipse [message #302365] |
Wed, 19 April 2006 11:47 |
Eclipse User |
|
|
|
Hi!
Before entering the topic I have to say, that I have asked the
subclipse-plugin-people for help already. However, they did not find a
solution for my problem.
I am working with Eclipse 3.1.2, subclipse 1.0.1 (current release), a
subversion-server 1.2.3-2 (opensuse 10.0), Microsoft Windows XP, Java
1.5.0_06) and have a reproduceable problem (on our machines in our
company) deleting a directory, that is under subversion control.
I simply do the following (in a blank Eclipse installation with the
subclipse-plugin installed via the Update-manager).
- Create a blank new Java project and share it via SVN (commit all new
files and directories).
- Create a new directory "myDir" and within that directory a class "AAA".
- Commit the changes.
- Try to delete the directory "myDir" (again in the java-view).
Eclipse now tells me, that the directory is read-only and whether I still
want to delete it. Answering "yes" ends in an error-dialog from Eclipse
with Undo and Abort button of that action. Aborting the action leaves the
project in an inconsistent state compared to the SVN repository (myDir
still exists, but the contained .svn directory is missing, therefore any
further update or commit fails).
The strange thing is, that eclipse seems to forget about the read-only bit
when closing and re-opening the project. So in case I answer "no" to the
question "Do you want to delete a read-only element?", close the project,
re-open it and try to delete the directory "myDir" again, everything works
fine.
Can anyone help me on that problem? The subclipse-people say, it has to be
some problem with Eclipse or the file-system. Well, I work on my local
file system and never had such problems. To my mind (although I did not
develop a plugin before) it has to be something in the interface between
SVN and Eclipse (Up to now, we work with CVS and there no such problem
occurred, yet). Thus, the question is whether the SVN plugin somehow may
influence the read-only-information on the directory information
controlled by Eclipse? Is there any locking mechanism where Subclipse may
do somthing wrong?
Best regards
Volker
PS: more subclipse information (including the installation documentation)
can be found on http://subclipse.tigris.org/
|
|
|
Powered by
FUDForum. Page generated in 0.03586 seconds
Home