"Renneberg, Volker (Bundeswehr)" <Volker.Renneberg.External@eads.com>
wrote on 04/18/2006 04:48:21 AM:
> I just used another of our development computers, installed eclipse
3.1.2 with
> subclipse 1.0.1 and reproduced the problem. We work an the
C:-Filesystem. All
> other operations work fine.
>
> To me it seems, that eclipse somehow remembers a read-only bit which
prohibits
> the deletion of the directory. Since closing and re-opening solves this
> problem (eclipse does not think, the myDir is read-only anymore) this
really
> seems to be an eclipse problem or a problem between eclipse and
subclipse.
>
> My question is, how do eclipse and subclipse interact - is it possible,
that
> some behaviour of subclipse during commit lets eclipse think, that a
directory
> is read-only??? I never programmed with eclipse. Is there any specific
mailing
> list of eclipse, where I can file this problem and get some help?
I would focus on figuring out what is causing stuff to be read-only to
begin with. I would also see if it is really read-only or not. If you
look in the Windows file system does it say the file is read-only?
Rather than doing a Close/Open cycle on the project have you tried
selecting the project and doing a Refresh?
Eclipse has an eclipse.platform Newsgroup for general questions and of
course there is a Bugzilla database as Eclipse.org as well. I think it
would be worth spending a bit more time on it here before asking Eclipse.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Apr 18 15:29:16 2006