[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Unknown icon decorators after adding project?

From: Nurmi, Marc A <marc.nurmi_at_eds.com>
Date: 2005-08-29 22:04:15 CEST

Yes, you are correct, the svn:needs-lock property is not set and the
files were read-only. I'm migrating projects from a ClearCase
repository and ClearCase uses the read-only attribute to indicate
whether or not the file is currently checked out.

It would be nice if Subclipse/Subversion would reset the read-only
attribute for the user when importing a project.

-----Original Message-----
From: Mark Phippard [mailto:MarkP@softlanding.com]
Sent: Monday, August 29, 2005 3:46 PM
To: users@subclipse.tigris.org
Subject: Re: Unknown icon decorators after adding project?

"Nurmi, Marc A" <marc.nurmi@eds.com> wrote on 08/29/2005 03:40:07 PM:

> After importing a project into a subversion repository as described in

> online help ("Import a New Project into a Subversion Repository"), the

> and package icons are decorated as expected with an orange cylinder in

> lower right corner. However, the java file and class icons are
decorated with
> a red minus sign. I have been unable to determine what this means.
> If I then delete the project from my workspace and then check it out
from the
> repository, it cleans this up and all icon decorators are orange
cylinders as
> expected. Is this a bug? What does the red minus indicate? It does
> appear to be documented anywhere. The SVN console does not show any
> I'm running Eclipse 3.1, Subclipse 0.9.33, and Subversion 1.2.0-r14790

> svnserve) on Windows.

The icon you refer to (red minus sign) will appear on any file that has
the read-only attribute set. Generally, this means that the
svn:needs-lock property is defined on the file. In your case, it sounds

like the files were read-only before you imported them.

I think there is a bit of a bug in Subversion here. Ideally, when you
committed those files (since you do not have the svn:needs-lock property

set on the files) it should have removed the read-only attribute. I
heard of people having Subversion commands like update and merge fail if
file was read-only in the working copy (and did not have svn:needs-lock


Scanned for SoftLanding Systems, Inc. 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 Aug 30 06:04:15 2005

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.