Community
Participate
Working Groups
Build ID: Eclipse 3.4 RC4 The update site now contains ONLY Ganymede support. The Subversive plan document, http://wiki.eclipse.org/Subversive_Plan states that the Subversive team is planning on supporting 3.3. http://ganymede-mirror2.eclipse.org/technology/subversive/0.7/update-site/ For example, the mylyn integration feature, features/org.eclipse.team.svn.mylyn_0.7.1.I20080612-1500.jar, has this requires clause. <import feature="org.eclipse.mylyn_feature" version="3.0.0" match="greaterOrEqual"/> Note that version 3.0.0 of Mylyn is the Ganymede release of Mylyn.
Support of Eclipse 3.3 is not removed from Subversive. The only one what you need is installing of Mylyn 3.0 for Eclipse 3.3.x. Corresponding update site are located at URL: http://download.eclipse.org/tools/mylyn/update/weekly/e3.3 P.S. At this moment I use Eclipse 3.3.1, Mylyn 3.0 and Subversive together without any problems. :-)
Please see bug #238469. Since Mylyn has overlapping feature jars, p2 cannot know which is the correct jar to install. As for your suggestion that you we ask our users to run off of the weekly update site, I'm not comfortable doing that. Our 3.3 users expect the stability that a year-old release offers them and adding a weekly update site could easily add instability. I've reopened the bug as you're going to have to react to whatever changes Mylyn makes and/or you'll have to make your own decision about shipping features that are known to break the feature identity requirements.
(In reply to comment #2) I read the bug #238469 and I see very small relation to Subversive itself. Moreover I agree with the Mylyn team that keeping compatibility with the plug-ins which does not have any dependencies from the version-specific Eclipse parts is important task. Practically, usage of improved Mylyn 3.0 APIs is "must be" requirement for our plug-in. We already used some APIs which help us a lot in order to improve integration of the Subversive plug-in with the Mylyn plug-in and we await for API changes in the Mylyn 3.0 descendants (please check the bug 229495 description and how it depends on the bug 212209). So, really I see no way to support Mylyn 2.3 and respect Eclipse guidelines (once again: bug 229495) simultaneously. Please note that simple removing of menu items enumerated in bug 229495 is not an option for us because it will overload our team members by useless "paper work" with bug reports which does not contain important information which will help to solve a problems. The second point is the weekly update site. This site will incrementally accumulate a fixes for the reported problems. After critical set of fixes is accumulated we will publish a release with the new service number. So, previously used update site support will not be removed until plug-in graduation is complete.
Bug #238469 talks about how there are two sets of Mylyn bundles that have the same versions, namely 3.0.0. This breaks the identity contract for bundles and since Subversive depends on this version, this has the potential to break Subversive installs. I've given use cases in bug #238469. I'm not suggesting you should pull Mylyn from your dependencies. Nor am I suggesting supporting 2.3. I agree that it is important for the Mylyn team to maintain compatible versions of their software. And I think they've already come up with some solutions that should allow for the release of compatible, yet differently versioned, releases of Mylyn. What I suspect will happen is that the Mylyn team will come up with a bundle versioning convention that will allow you to depend on a range of bundles. So switching should be relatively painless. However, I strongly urge you to move quickly behind them to release a point release of your own that does not depend on their 3.0.0 bundles. If they do something like that, and if you release a point release shortly after them, users will only have to use one Subversive and one Mylyn update site to get either a 3.3.2 or a 3.4 client.
Regarding to Jed's comment to bug 238469 (dated 30.07.2008) I'm closing this bug, cause Mylyn 3.x is the obvious dependency for normal integration and bug reporting. Jed, have I understood you right?
