Mark Phippard wrote:
> Properties are the only way the project folder will show in Synch view as
> changed. Did you see this in the earlier releases? I usually change the
> subclipse:tags property on our project folders, so if you have been using
> Synch to update them you would have likely run into this before. I do not
> believe we have made any changes in recent releases that would effect
I always use sync view to run update and switch to Package Explorer
only when update does not work from sync view. Strangely, I haven't seen
this issue before... since I reported it against some ancient Subclipse
>> BTW, at some point I've been suggesting to introduce special node in
>> sync and history views to show properties, so it would be possible to
>> treat it as a first class change, e.g. run comparison editor, update,
>> etc. I don't remember what was the conclusion or arguments against it?
> Generally I think it would be great, but I would not have the faintest
> idea how to do it. Also, there are certain things that cannot be done, so
> the options would have to be exposed carefully. For example, properties
> cannot be committed/updated independent of the contents of a file.
> Certainly being able to see and compare property changes would be nice.
>> PS: that locking error is probably unrelated issue, but it look
>> suspicious too.
> I think you have reported it before.
That is interesting. :-)
> I do not really have any idea where to look on it, I have taken a look in
> the past. I agree that it is not likely to be directly related to the
> same issue.
Maybe you can put some debug code, e.g. capture what thread created
lock and stack trace for lock creation. Then this assertion will give
little more information.
PS: btw, it is now possible to hook up Subclipse's IssueZilla with
Mylar's Task List view...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Aug 9 16:04:20 2006