[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?

[Mickael Istria (JIRA)]

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

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

A good link to a stable repo is http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.30.5.Alpha/
Also, I'd encourage to create and use you own target platform since you'll probably won't need all of JBT target-platform/repositories to develop RedDeer.

I think it makes sense that you don't use the parent pom: it's very coupled with JBT concerns, so 2/3 of it would be useless in your case. For the remaining third (source features, code-coverage, repository facade...) you can simply copy-paste some bits in your RedDeer parent pom.
                
> 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