Community
Participate
Working Groups
I20051102 Since JDT UI now has a job to do its own initialization, we now have 2 jobs running on startup, which is confusing for the user. We should only have the JDT UI job.
One solution would be for JDT UI to call JavaCore#initializeAfterLoad() inside their job, and we remove the job spawning in this method.
Changed JavaCore#initializeAfterLoad(...) to not schedule a job and do the work in the same method.
Verified for 3.2 M4 using build I20051212-0010