Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356960 - [Subclipse] Verify required version for Subclipse plugin
Summary: [Subclipse] Verify required version for Subclipse plugin
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 0.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 0.9   Edit
Assignee: Alvaro Sanchez-Leon CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-07 11:56 EDT by Sebastien Dubois CLA
Modified: 2011-09-15 08:16 EDT (History)
3 users (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 Sebastien Dubois CLA 2011-09-07 11:56:47 EDT 
Right now the org.tigris.subversion.subclipse.core plugin is required with minimal version 1.6.18.  This version is the most recent version for subclipse.  To support older Eclipse versions (3.5, 3.6), it is desirable to lower the version to the earliest possible version whose API is supported by the SVN connector.  This needs to be investigated.
Comment 1 Alvaro Sanchez-Leon CLA 2011-09-07 12:57:11 EDT 
Subclipse 1.6.18 is the latest support for Eclipse 3.2 to 3.7
http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA

The CQ https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5289 was raised to use 1.6.18

Is it really needed to support lower than 1.6.18 ? Interested users shall be able to upgrade to 1.6.18.
Comment 2 Sebastien Dubois CLA 2011-09-07 13:21:46 EDT 
EECS with Eclipse 3.6 has 1.6.17, so I think that if we check compatibility with 1.6.17 that should be enough.
Comment 3 Steffen Pingel CLA 2011-09-07 16:00:31 EDT 
Don't worry to much about the version. Use the constraint that makes sense technically and we'll update the CQ accordingly if needed.
Comment 4 Alvaro Sanchez-Leon CLA 2011-09-14 18:41:38 EDT 
The minimum versions has now been tested and updated to 1.6.17, 

is it necessary to re-open the cq to reflect this ?
Comment 5 Steffen Pingel CLA 2011-09-15 04:37:40 EDT 
No, that's fine. Since it's a works-with dependency we don't need to update the CQ when the version changes.
Comment 6 Alvaro Sanchez-Leon CLA 2011-09-15 08:16:44 EDT 
Implemented