Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336855 - [Demo] Launch configurations of RAP demo broken
Summary: [Demo] Launch configurations of RAP demo broken
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: Demo (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 12:50 EST by Benjamin Wolff CLA
Modified: 2011-02-11 04:20 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Wolff CLA 2011-02-10 12:50:18 EST
The current launch configurations of the RAP demo unnecessarily start the JUnit plug-ins. The required org.hamcrest.core plug-in is not in the start configuration so there is a missing constraint for the JUnit plug-ins resulting in an error flood upon launching the configuration.
Comment 1 Ivan Furnadjiev CLA 2011-02-10 13:10:51 EST
Are you talking about org.eclipse.rap.demo or other demo? Just checked Controls Demo.launch and RAP Workbench Demo.launch and I can't find any problem. This is a strange dependency to org.hamcrest.core. Maybe you have a different JUnit plugin from the one in the RAP target platform??!!
Comment 2 Benjamin Wolff CLA 2011-02-10 13:27:41 EST
Hi Ivan,

yes, i'm refering to the org.eclipse.rap.demo plug-in from CVS HEAD.

I just found the cause, it was my fault, sorry.

I have the JUnit 4.8.1 plug-in installed in my target platform which needs the org.hamcrest.core plug-in. The RAP demo launch configurations start the "org.junit" plug-in, and because i have two "org.junit" plug-ins both are started causing the missing constraint to hamcrest.

But i wonder why the org.junit plug-in is in the start configuration anyway?? Is it used in the demos??
Comment 3 Ivan Furnadjiev CLA 2011-02-11 04:20:25 EST
Yes... your are right - org.junit bundle is not needed in the launch configurations. Fixed in CVS HEAD.