Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358496 - Drop support for eclipse 3.5
Summary: Drop support for eclipse 3.5
Status: CLOSED FIXED
Alias: None
Product: SWTBot
Classification: Technology
Component: SWTBot (show other bugs)
Version: 2.0.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0.5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 308425 359024
  Show dependency tree
 
Reported: 2011-09-21 17:48 EDT by Ketan Padegaonkar CLA
Modified: 2011-09-27 05:02 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ketan Padegaonkar CLA 2011-09-21 17:48:11 EDT 
Adding support for macosx cocoa requires use of junit 4.7, this is only shipped with eclipse 3.6 and higher.

I'd like to open this bug to consider dropping support for eclipse 3.5 going ahead given that eclipse 3.5 is a little over 2 years old.
Comment 1 Ketan Padegaonkar CLA 2011-09-21 17:52:30 EDT 
Checked into revision 019dacc12d4cca123886abbc50ac9b3131bdf071. Can be reverted if needed.
Comment 2 Mickael Istria CLA 2011-09-22 07:58:30 EDT 
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?
Comment 3 Ketan Padegaonkar CLA 2011-09-22 11:22:30 EDT 
(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.
Comment 4 Mickael Istria CLA 2011-09-26 12:56:45 EDT 
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.
Comment 5 Ketan Padegaonkar CLA 2011-09-26 13:10:42 EDT 
(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.