[jdt-core-dev] Change in JavaCore#initializeAfterLoad()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jdt-core-dev] Change in JavaCore#initializeAfterLoad()

From: Jerome Lanneluc <jerome_lanneluc@xxxxxxxxxx>
Date: Thu, 17 Nov 2005 15:57:52 +0100
Delivered-to: jdt-core-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/jdt-core-dev>
List-help: <mailto:jdt-core-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jdt-core-dev>, <mailto:jdt-core-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/jdt-core-dev>, <mailto:jdt-core-dev-request@eclipse.org?subject=unsubscribe>

JavaCore#initializeAfterLoad() doesn't schedule a job any longer. So if you
patch I20051116 with the latest JDT Core, you might see the UI frozen on
startup while JDT Core is being initialized.
JDT UI is changing its behavior at the same time, and you will no longer
see this problem in next integration build.

Jerome

Follow-Ups:
- Re: [jdt-core-dev] Change in JavaCore#initializeAfterLoad()
  - From: Dirk Baeumer

Prev by Date: [jdt-core-dev] Failing JDT UI tests
Next by Date: Re: [jdt-core-dev] Change in JavaCore#initializeAfterLoad()
Previous by thread: [jdt-core-dev] Failing JDT UI tests
Next by thread: Re: [jdt-core-dev] Change in JavaCore#initializeAfterLoad()
Index(es):
- Date
- Thread

Breadcrumbs