Community
Participate
Working Groups
Bug 196617 has been resolved, but there are people who have to work on Eclipse 3.2-based IDEs and thus are unable to upgrade to Mylyn 2.1. I think this is a significant enough problem for a patch to 2.0 to be released. Could you please consider this? I can probably knock something together myself, but I'd much rather distribute an official version of Mylyn than a self-built job, and I'm sure I can't be the only person in this situation.
It occurs to me that given comment #28 in bug 196617 and my failed attempts to intall the Jira connector through the update manager, perhaps you have already attempted to release an update. But the download site is broken. a) The Jira connector is shown as having a version qualifier indicating that it's 2 months newer than the rest of the 2.0 components. b) The update manager won't let you install the Jira connector, as it demands a core mylyn feature version the same as its own, but the core e3.2 Mylyn 2.0 feature is 2 months older. c) If you download the Mylyn Extras zip file manually from the link on the download site, the Jira connector enclosed does not match those advertised on the update site - it is older.
Kevin: I have relaxed the dependency requirements of the JIRA Connector to work with any Mylyn 2.0 compatible release. Tonight's weekly build will include this change. Please try to install it and post your experiences, reopening if you have any problems: http://www.eclipse.org/mylyn/downloads/
Created attachment 80182 [details] Stack backtrace I'm testing with a clean installation of Eclipse 3.2.2. After installing the core Mylyn 2.0.0 features, I went on to try to install JIRA. Upon selecting anything in Integration category from download.eclipse.org/tools/mylyn/update/weekly/extras I get a NullPointerException, and I can't proceed with installation. Mind you, I find I'm also getting that with the Mylyn 2.0.0 extras.
I assume that you are using the "Search for new features..." option? The "Search for updates" option is broken on 3.2. What's the exception you are seeing (please paste from Error Log view).
I pasted a backtrace above. That was using "Search for new features". I'm going to run through it again from scratch on a different machine now, noting the steps in detail. 1) Download eclipse-SDK-3.2.2-win32.zip, and install into C:\Program Files\Eclipse322\ 2) Run Eclipse.exe 3) Specify a new workspace directory, set as default 4) Close welcome screen, Software Updates > Find and Install... > Search for New Features 5) Add site download.eclipse.org/tools/mylyn/update-archive/2.0.0/e3.2, and select it. 6) Install everything there except the Trac connector, running the update in the background. 7) Restart when prompted. 8) Go back to Search for New Features. 9) Add site download.eclipse.org/tools/mylyn/update/weekly/extras, select it. 10) This time, there's no problem selecting the JIRA update. Interesting! But if I go back and add the 2.0 Extras site and search it alongside the Extras Weekly Build site, which was what I was doing with yesterday's attempt, I get the NullPointerExceptions from the attachment. So the problem's apparently triggered by having two sites for the same component (albeit with different versions). So, it's now possible to get the JIRA fix for Mylyn 2.0 through the update manager. But there are still problems with the update site, as first mentioned in comment #1. 1) Eclipse 3.2 users can't install any connectors or the UI Experimentation from the 2.0 Extras site, as they all demand newer versions of the core Mylyn feature than are supplied with 2.0 for 3.2. I can now install the connectors from the Weekly Builds site, but there's as yet nothing on the download site to suggest this workaround. 2) Mylyn 2.0 users can't install the Generic Issue Tracker connector from the Extras Weekly Builds site, as it needs Mylyn 2.1. So the 2.0 sites are inconsistent and can't be installed. There's also nothing there to suggest that users should try the Weekly Builds instead. And there's still no path to install the Generic connector on 2.0 for 3.2. I guess it's time to turn this into an update site bug, or create a separate report.
I've added an entry to the Wiki FAQ covering the Mylyn 2.0/JIRA 3.10 issue.
I'm still trying to figure out how feasible it is for us to have all the extras support Mylyn 2.0. The problem is that we are evolving those plug-ins quickly and doing this would be at the cost of improving them along with the Mylyn API changes. Steffen: I've added this to the agenda for the next conference call, let's discuss, taking Kevin's input from here and bug 206116, and then report back.
Due to changes in the API the latest weekly builds of the JIRA connector do not work with Mylyn 2.0 anymore but depend on the current weekly version (which requires Eclipse 3.3 or above). I have updated the FAQ. At this point we don't have the resources to support additional Eclipse version and I am not sure we have enough indication that it is worth back-porting the fix to 3.2. Mik, what are your thoughts on a 2.0.1 maintenance release of the JIRA connector?
Actually, I think there are - like us - a lot of Eclipse 3.2 users out there. As for me, I am forced to work with the Rational Software Architect, which is based in 3.2 and not expected to go to 3.3 any time soon. So I believe that each and every user of Rational stuff is going to stay on 3.2... Could you please, as a first step, publish one consistent set of plugins (Mylyn core and extras) that is going to install ok? This might also improve the Mylyn community since I have heard of first time users trying out Mylyn 2.0 that they are going to drop it because of the many installation issues. Also, does the issues with Jira 3.10 still persist with 3.12? Thanks for any input and keep up the good work! Andreas
Steffen: as part of the Mylyn 2.2 release let's do the best we can for improving the Eclipse 3.2 situation. This might mean putting up a separate Mylyn 2.0 specific update site of extras.
Mik, I opened bug 212995 to fix the 2.0.0 update site. Essentially you just need to move away the old 2.0.0 extras directory and unzip the extras archive. This will fix the installation problems on 3.2. I ran a quick test on 3.2 with the JIRA feature from the extras zip archive. The version errors with JIRA repositories running 3.10 or later persists (bug 196617). Other than that the connector breaks on JIRA 3.11 or later due to changes in the SOAP interface (bug 13529). We could consider putting out an updated release if a back-port of fixes for these bugs was contributed. Alternatively we could release the latest version from October that was still working with 3.2. Kevin, did you run into any problems with the version you got from the weekly extras update site?
I've been continuing to use Mylyn 2.0 with that weekly update version of the JIRA connector from my October comment without problem.
Thanks Kevin. Mik, the best strategy might be to make a 2.1.2 release of the 2.1 JIRA connector that has a relaxed dependency and will install into Eclipse 3.2 with Mylyn 2.0 . The correct bug that describes the fixed made for JIRA 3.11 is bug 203401.
The 2.0.0 update site has been fixed and a 2.1.2 release of the JIRA connector that can be installed with Mylyn 2.0.0 has been uploaded to the 2.1 extras update site: download.eclipse.org/tools/mylyn/update-archive/2.1.0/extras That version of the JIRA connector works properly on Eclipse 3.2 and supports JIRA 3.10 and later.
