Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313864 - [Tooling] Templates: Unable to run the templates / deadlock
Summary: [Tooling] Templates: Unable to run the templates / deadlock
Status: RESOLVED WORKSFORME
Alias: None
Product: RAP
Classification: RT
Component: Tools (show other bugs)
Version: 1.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://build.eclipse.org/technology/e...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 03:04 EDT by Markus Knauer CLA
Modified: 2010-05-21 05:07 EDT (History)
0 users

See Also:

Attachments
stacktrace (16.74 KB, text/plain)
2010-05-21 03:04 EDT, Markus Knauer CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Knauer CLA 2010-05-21 03:04:11 EDT 
Created attachment 169473 [details]
stacktrace

# download the RCP packages for Helios RC1 (or use RAP 1.3RC1 with Eclipse 3.6RC1)
# switch to RAP target
# create a new plug-in project and select one of the RAP templates in the wizard
# try to start is by using the included launch configuration

It will fail with this message:

!MESSAGE While loading class "org.eclipse.ui.PlatformUI", thread "Thread[Framework Event Dispatcher,5,main]" timed out waiting (5000ms) for thread "Thread[Start Level Event Dispatcher,5,main]" to finish starting bundle "org.eclipse.rap.ui.workbench_1.3.0.20100518-1222 [8]". To avoid deadlock, thread "Thread[Framework Event Dispatcher,5,main]" is proceeding but "org.eclipse.ui.PlatformUI" may not be fully initialized.

A quick fix was to set the start level of the plug-in org.eclipse.rap.ui.workbench to 5
Comment 1 Holger Staudacher CLA 2010-05-21 05:07:13 EDT 
I tested the templates with a clean and dirty RC1 installation. Everything works as expected. So, I will close the bug with WORKSFORME. If the problem occurs again please feel free to reopen the bug.