| Summary: | [api] Enable the possibility for connectors to describe their specific attributes | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alvaro Sanchez-Leon <alvaro.sanchez-leon> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | kilian.matt, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 330616 | ||
|
Description
Alvaro Sanchez-Leon
initial draft implementation is under the "versionsIntegration" branch Alvaro, what is the purpose of these key/values? Can you give an example? (In reply to comment #2) > Alvaro, what is the purpose of these key/values? Can you give an example? Yes, In a wizard we can have multiple selection values that are dependent of the specific version control system. e.g. changeset selection via a query with specific HAS/HAS NOT labels, branches, activities, etc.. So the key values can be later presented to the user. In the tasks framework we have used methods that return booleans to describe the capabilities of repositories, e.g. AbstractRepositoryConnector.hasLocalCompletionState(). Is this something similar for the versions framework? 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 |