software rot.
On Dec 20, 2010, at 1:12 PM, Pascal Robert wrote:
> BTW, I was able to make my changes by putting the project in another
> workplace. But what's weird is that I got back to my main workplace and I
> don't have any deadlocks while saving the component. Strange.
>
>> I'm getting
BTW, I was able to make my changes by putting the project in another workplace.
But what's weird is that I got back to my main workplace and I don't have any
deadlocks while saving the component. Strange.
> I'm getting the exact same problem. Does your deadlocks occurs when you save
> changes m
>I'm getting the exact same problem. Does your deadlocks occurs when you save
>changes made in a component?
I did not notice that first time. But now I'd say YES.
2010/12/18 Q :
> I spoke to mike about this recently, it's a race condition related to locking
> used for validation and validation c
I spoke to mike about this recently, it's a race condition related to locking
used for validation and validation caching, it's a difficult one to fix, and
the only workaround I can think of would be to disable component validation.
On 18/12/2010, at 6:22 AM, Johnny Miller wrote:
> I have even a
I have even a stranger problem. Not only did I have this problem in one
project but I created a new project (that was a new version of the other
project) and I had the same problem in a component that had the same name. I
didn't copy and paste anything over because I was afraid that the old fi
It doesn't happen to me often but when it doesn't happen, it is when saving
changes to a component - specifically in the html editor I believe.
Tim Worman
UCLA GSE&IS
On Dec 17, 2010, at 8:28 AM, Pascal Robert wrote:
> I'm getting the exact same problem. Does your deadlocks occurs when you save
I'm having the same problem. I turned off automatic building and just
manually run builds and haven't had a problem since.
Joe
On Fri, Dec 17, 2010 at 8:28 AM, Pascal Robert wrote:
> I'm getting the exact same problem. Does your deadlocks occurs when you
> save changes made in a component?
>
>
I'm getting the exact same problem. Does your deadlocks occurs when you save
changes made in a component?
You should report your problem to JIRA, see:
http://issues.objectstyle.org/jira/browse/WOL-1198
> Hello all
> I'v recently upgraded my dev environment to Eclipse 3.6 and a WOLips
> versio
Hello all
I'v recently upgraded my dev environment to Eclipse 3.6 and a WOLips
version recommended in wiki
I like some new features but now I regularly bump into Eclipse
deadlock and have to force quit it.
Here is the jstack dump from the last deadlock.
I am writing here and not Eclipse support as
