RE: [Subclipse-users] Exception in Eclipse's log for closed Projects

Reopened a bug within eclipse, but see also the evaluation:
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=111862
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=111862>

Product/Component: Platform / IDE

------- Comment #6 from john_arthorne@ca.ibm.com 2007-03-20 09:55
-------

I'll move to UI for comment then. They may be able to avoid causing a

decoration on closed projects. However, there is nothing in the
decoration API

contract that says closed projects will never be decorated, so the
decorator in

question should really be handling the case more gracefully (check for
closed

projects and/or avoid logging).

________________________________

From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Monday, March 19, 2007 1:38 PM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] Exception in Eclipse's log for closed
Projects

On 3/19/07, Markus Schlegel <schlm3@gmail.com> wrote:

        Don't you think, that writing Megabytes of logfiles (I have 10
files, ".log", ".bak_0", ..., ".bak_9", each of 1MB and the same
timestamp) does not slow down eclipse drastically?
        As far as I can see, Subversion recognises that the resource is
closed (by receiving an exception from setSyncInfo), so far so good. If
it is normal that Eclipse asks for the decoration of a closed resource,
Subversion should simply ignore that call rather than throwing that
Exception.
        If it is not expected to be asked for the status of a closed
resource, I think I should rather file a bugreport against eclipse.org,
right?

It could not hurt to file a bug with Eclipse. I cannot reproduce the
problem and at least if we filed it then maybe they could clarify on
whether they are doing this intentionally or not, and if so in what
situation.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/