Bugzilla – Full Text Bug Listing
| Summary: | support drag and drop for task working sets | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P4 | CC: | shawn.minto, steffen.pingel |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 353153 | ||
|
Description
Steffen Pingel
How did you make task working sets appear in the Package Explorer view? I have Package Explorer view to show working sets as root elements and it only shows Java working sets only and "configure working sets" in the view menu also show only the Java working sets It requires some tweaking: bug 214046 . Closing this bug as it works now and nothing related was changed in Mylyn. It was probably due to working sets not being persisted properly caused by a 3rd party plug-in. It turns out that the package explorer adds a different type of element to the working set when elements are dropped on a task working set: <item elementID="=org.eclipse.mylyn.trac" factoryID="org.eclipse.jdt.ui.PersistableJavaElementFactory"/> If working sets are configured through the working set dialog this type of element is added: <item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/org.eclipse.mylyn" type="4"/> Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |