| Summary: | mylyn 3.8 release broke some old connectors | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> |
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | ||
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Eugene Kuleshov
Those connectors need to be updated. Please see bug 360301. *** This bug has been marked as a duplicate of bug 360301 *** Steven, I know it need to be updated, but unfortunately it is not possible. Hence request to provide compatibility plugin. I understand that it is unfortunate that the classes are no longer available but we generally do not provide backwards compatibility support when making changes to internals. If you are unable to upgrade the connector you would need to downgrade to a previous Mylyn release. Older releases can be found in the archive: http://eclipse.org/mylyn/downloads/archive.php. Steven, you should be aware, that it is next to impossible to downgrade Mylyn in any Eclipse, because it is packaged together with Platform. Please reconsider providing backward compatibility layer. I'm sorry but we don't have capacity to provide a compatibility layer. I would recommend to start with the Eclipse SDK and install Mylyn on top of that or use an older packaged Eclipse platform release to consume a previous Mylyn release. Well, you had the "capacity" to break existing connectors... Very frustrating. Starting from Eclipse SDK is not really an option either, because of project interdepencencies. Eclipse release train was invented for that reason. |