| Summary: | [api] provide connector API to retrieve repository persons | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Benjamin Muskalla <b.muskalla> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | doug.janzen, shawn.minto |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Benjamin Muskalla
I am wondering if we should consider this part of repository configuration data or whether it makes more sense to provide a cache on the framework level for identities? Do you have a concrete example for an implementation? I know that Rally has a defined set of users from the repository that are managed as a part of the configuration so that only valid users can be selected in user fields. This is now supported for specific attributes at least but it sounds reasonable to support this on a per repository level as well. Feel free to propose a concrete API for this functionality. 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 |