Community
Participate
Working Groups
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.
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??!!
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??
Yes... your are right - org.junit bundle is not needed in the launch configurations. Fixed in CVS HEAD.