Summary: | Can't open mylar task view - NoClassDefFoundError | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Brett Connor <brettconnor+b> |
Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> |
Status: | RESOLVED DUPLICATE | QA Contact: | |
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 0.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Brett Connor
2005-12-19 05:23:33 EST
Oops, just changed the summary, wasn't classnotfound it is NoClassDefFoundError. Everything I do now pulls up the same error referring to various Mylar classes such as org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/eclipse/mylar/ui/actions/AbstractApplyMylarAction) so it looks more like Mylar simply failed to install I guess, though nothing suggesting this appeared in the log during / after install, until I tried to do something. Yes, it's annoying that Eclipse fails to inform of unsuccesful installs, and this is almost certainly a failed install (e.g. a 3.2 version into 3.1). Could you please try following these instructions: http://eclipse.org/mylar/doc/faq.php#install-failure Archived releases of Mylar can be found by using an update site with the version in the path, like the example below (I'll make this more clear on the download page): download.eclipse.org/technology/mylar/update-site/0.4.4/e3.2 (for Eclipse 3.2) I hope that you don't have to move back to 0.4.4, so if the install still fails please send me your .metadata/.log file. Let me know how it goes. Also, please consider backing up your tasklist.xml file before doing the next upgrade, although your tasks should simply reappear once Mylar is installed correctly: http://eclipse.org/mylar/doc/faq.php#tasklist-blank I've repeated the re-installation sequence using the same download site http://download.eclipse.org/technology/mylar/update-site/e3.1, this time it seems good. It installed a different version this time - 0.4.6.1 vs 0.4.6 thismorning. As far as I can tell that's the only difference. Is this something you would expect? Anyhow it seems shiny so far. Thanks! Yes, sorry I meant to update this report after I realized what it was but was traveling yesterday. This fix went into 0.4.6.1, and was the main reason for putting out 0.4.6.1. It was a race condition during plug-in initialization that could cause startup failure. Glad that it works for you now. *** This bug has been marked as a duplicate of 121326 *** |