[jbosstools-issues] [JBoss JIRA] (JBIDE-13843) Investigate use of SWTBot 2.1 (and org.junit_4.11) in target platform

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778071#comment-12778071 ] 

Mickael Istria commented on JBIDE-13843:
----------------------------------------

Newer snapshot of SWTBot fixes compatibility with Junit 4.11 and Hamcrest 1.3.
Release of SWTBot should happen by the end of June (ideally same day as Kepler).

If we have issues in JBT tests because of SWTBot bug #404346, we could mirror a newer snapshot and use it in TP until the release gets out.
                
> 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