[jbosstools-issues] [JBoss JIRA] (JBIDE-13843) SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?

Nick Boldt (JIRA) jira-events at lists.jboss.org
Sat Mar 23 20:18:41 EDT 2013


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

Nick Boldt commented on JBIDE-13843:
------------------------------------

Red Deer should be using the JBT TP instead.

Latest released one: http://download.jboss.org/jbosstools/updates/kepler/ (points to 4.30.5.Alpha)
Latest unreleased one: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.30.5.Alpha3-SNAPSHOT/

Or just use our parent pom (version 4.1.0.Alpha2) [1] and you'll get access to both of the versions above w/o needing to define anything extra in your root pom.

[1] https://github.com/jbosstools/jbosstools-central/blob/master/pom.xml#L8

                
> SWTBot 2.0.5 depends on org.junit4, which has been removed from Eclipse 4.3M6. Can we use SWTBot 2.1 instead?
> -------------------------------------------------------------------------------------------------------------
>
>                 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
>             Fix For: 4.1.0.Alpha2
>
>
> 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


More information about the jbosstools-issues mailing list