| Summary: | Task UI error running plugin unit tests after installing mylyn builds | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Ken Leung <plcnkl> |
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> |
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | overholt, sgehwolf |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ken Leung
If you open the launch configuration and validate the plug-ins are there any errors? Is the Target Platform in the preferences configured correctly? *** Bug 356114 has been marked as a duplicate of this bug. *** If I had to guess, I'd say something may be missing the underlying RPMs. Ken is speaking with the Fedora maintainer of Mylyn Builds as I type this. (In reply to comment #3) > If I had to guess, I'd say something may be missing the underlying RPMs. Ken > is speaking with the Fedora maintainer of Mylyn Builds as I type this. I'm said maintainer :) I don't think this is a bug. Neither an upstream bug (here) nor a bug in Fedora's eclipse-mylyn* packages. The problem Ken was facing had to do with having a mix of RPM installed bundles as well as having some upstream sources available in his workspace. For some of them the versions didn't match, so I don't think this had ever a chance to work. Ken, I suggest to prepare a workspace with mylyn builds sources from upstream only. I'm aware that this might require to clone several mylyn repositories and import plug-ins into your workspace appropriately. So far my assessment of the problem, anyhow. Thanks for the clarification. I'll mark this bug as resolved. Feel free to reopen if you have steps to reproduce this with the standard Mylyn packages. Ken, you can also set your target to one of the pre-defined target environments to avoid version conflicts: http://wiki.eclipse.org/Mylyn/Contributor_Reference#Target_Environment |