| Summary: | Extend AbstractTaskReference and provide default impl | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Benjamin Muskalla <b.muskalla> |
| Component: | Mylyn | Assignee: | Benjamin Muskalla <b.muskalla> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | caniszczyk, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Benjamin Muskalla
Agreed. The current API is not very extensible and should be based on resources rather than AbstractTaskReference. Let's discuss that on a call before we dive into the implementation. I don't have any straight forward ideas how we can best do this. Would be nice to see this in the next release. Benjamin, can you join next weeks Mylyn call to discuss? I have added it to the agenda. After the discussion on the call today, we need to find the right place to host this adapter. As Versions should not depend on Tasks, we would need to move AbstractTaskReference and a new default implementation to Versions (or create new API if you want to call it like that). Steffen, if you want, I can take a first pass on this beginning next week. That sound good to me. Benjamin, will you have time to look into this? Let's make time for it :) Benjamin, to get this into 3.6 / Indigo we would need a patch by tomorrow. Is that realistic? Not really. Let's do this after Indigo. I want to ensure that the API we do here is not some hectic last-day activity. |