| Summary: | [api] provide mechanism for adding AttributeContainer to RepositoryTaskData | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Baybora Aksoy <berbay> |
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | mjmeijer, robert.elves, shawn.minto, steffen.pingel |
| Version: | 2.0 | ||
| Target Milestone: | 3.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 226822 | ||
|
Description
Baybora Aksoy
Rob: thoughts? This seems like a good idea since it could get very ugly when trying to store complex data structures within the RepositoryTaskData. This would help clean things up. Note to self: add this capability to RepositoryTaskData, not AttributeContainer to avoid cycles issue bug 224009: [api] make all task data externalization classes final https://bugs.eclipse.org/bugs/show_bug.cgi?id=224009 May make this impossible. Also foresee problems due to current deepCopy() using (de)serialization. *** Bug 193225 has been marked as a duplicate of this bug. *** Done. The TaskData class which supersedes RepositoryTaskData now has a root attribute of type TaskAttribute. Objects of type TaskAttribute can contain other TaskAttribute object which are can be created by invoking TaskAttribute.createAttribute(). |