| Re: [eclipse-dev] I20030604 for 3.0 M1 go from JDT/Core |
I second it - it is my experience too that deadlocks during import seem
more frequent than before.
Regards,
Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745 T/L 969-2745
Fax. 905 413-4854
Jeff
McAffer/Ottawa/IBM To: eclipse-dev@xxxxxxxxxxx
@IBMCA cc:
Sent by: Subject: Re: [eclipse-dev] I20030604 for 3.0 M1 go from JDT/Core
eclipse-dev-admin@
eclipse.org
06/05/2003 01:35
PM
Please respond to
eclipse-dev
This does not seem to be all that rare. We are seeing reproducable cases
here.
I suggest we look into this more carefully and perhaps come up with a
workaround. Otherwise, it is difficult to selfhost.
Jeff
"Philippe P Mulet"
<philippe_mulet@xxxxxxxxxx> To:
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin@xxxxxxxxxxx cc:
Subject: [eclipse-dev]
I20030604 for 3.0 M1 go from JDT/Core
06/05/2003 12:56 PM
Please respond to eclipse-dev
We are aware of a rare deadlock situation during plugin import (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=37274), but this isn't a
regression.
Thus not a stop ship for 3.0-M1.
GO from JDT/Core
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev