Hi Mickael,
Today we started testing JBT 4.1.0.Alpha2 and noticed that this is quite a big problem for us. Most of our tests fail with something like this:

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoSuchMethodError: org.hamcrest.core.IsAnything.any(Ljava/lang/Class;)Lorg/hamcrest/Matcher;)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)

Right now we don't know how to overcome this in automated jenkins test runs - swtbot always takes the newest version of hamcrest from the kepler platform, so even adding older hamcrest repo wouldn't help here. Do you have any suggestion for us? :)

Also, what will be the fix in SWTBot? If you fix it to work with the new hamcrest, it won't work with the older version, right? So this new swtbot will not be able to work with Juno with older hamcrest then?

Thanks,
Martin

On 28. 3. 2013, at 16:04, Mickael Istria <mistria@redhat.com> wrote:

Hi all,

Someone reported an issue in SWTBot 2.1.0 using Kepler M6 because of an API change in hamcrest. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 (release train ships a newer version of hamcrest).
It affects only *some* SWTBot methods, and most of SWTBot is still working (tests report 22 failure for 413 tests https://hudson.eclipse.org/hudson/view/SWTBot/job/swtbot-tycho-e4.2/ ).

In case you notice that our tests fail because of this issue, please tell me so I'll raise the priority of this bug and try to get it fixed ASAP.

Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev

--
Martin Malina
JBoss QA Engineer
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno, Czech Republic

Tel.: +420 532 294 265