[
https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13843:
----------------------------------------
what is the status of this ? can we just use the old swtbot for now
or do we need later for kepler ?
Nope, see bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=404346 . SWTBot needs to work
with Kepler
if we do need it why aren't swtbot releasing a kepler specific
one to at least have somthing working?
That's something I have been working on for the last days, but I still notice some
issues before getting a Kepler-friendly release of SWTBot (see bug dependencies).
We're using SWTBot 2.1.1 and org.junit_4.11 for now, until
something better comes along. Seems not to be crashing all our tests, so I suppose this
can be closed as fixed.
Just a reminder that we are using a 2.1.1-SNAPSHOT. 2.1.1 release will come as soon as bug
404346 is fixed. The issues between SWTBot and Kepler only affect some methods of SWTBot
that we're not using in JBT, so the incompatibility is not yet a blocker for our
usage.
Investigate use of SWTBot 2.1 (and org.junit_4.11) in target
platform
---------------------------------------------------------------------
Key: JBIDE-13843
URL:
https://issues.jboss.org/browse/JBIDE-13843
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform, testing-tools
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 4.1.0.Beta2
Eclipse 4.3M5a contains:
{code}4.3milestones/S-4.3M5a-201302041400/plugins/org.junit4_4.8.1.v20120705-112236.jar{code}
But in Eclipse 4.3M6, the only JUnit available is:
{code}4.3milestones/S-4.3M6-201303141330/plugins/org.junit_4.11.0.v201303080030.jar{code}
So, we need to see if a newer SWTBot can be used which depends on org.junit instead of
org.junit4.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira