| Summary: | Drop support for eclipse 3.5 | ||
|---|---|---|---|
| Product: | [Technology] SWTBot | Reporter: | Ketan Padegaonkar <KetanPadegaonkar> |
| Component: | SWTBot | Assignee: | Project Inbox <swtbot-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mistria |
| Version: | 2.0.4 | ||
| Target Milestone: | 2.0.5 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 308425, 359024 | ||
|
Description
Ketan Padegaonkar
Checked into revision 019dacc12d4cca123886abbc50ac9b3131bdf071. Can be reverted if needed. Ketan, does this refactoring means that most fragments to support several versions of Eclipse and JUnit become useless and are removed from the master branch? (In reply to comment #2) > Ketan, does this refactoring means that most fragments to support several > versions of Eclipse and JUnit become useless and are removed from the master > branch? Yes that is correct. There's no more "conditional compiling" based on versions of junit and eclipse, because the baseline is eclipse 3.6 which has most of the APIs required to run SWTBot. Since from 3.6, Eclipse ships a org.junit with version superior to 4, and removed the old org.junit4 (or make it an "alias" to org.junit 4.x - http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes ); you could also remove the fragment that depends on org.junit4 and unify all these org.eclipse.swtbot*junit stuff. (In reply to comment #4) > Since from 3.6, Eclipse ships a org.junit with version superior to 4, and > removed the old org.junit4 (or make it an "alias" to org.junit 4.x - > http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes ); you could also remove > the fragment that depends on org.junit4 and unify all these > org.eclipse.swtbot*junit stuff. Opened bug 358933 to track dropping JUnit 3.x support. |