| Summary: | [discussion] refine changeset API | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Kilian Matt <kilian.matt> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | caniszczyk, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 334759, 334761, 334784, 338478, 338547, 338669, 354670 | ||
| Bug Blocks: | |||
|
Description
Kilian Matt
For a generic task-changeset connector, we would need an api for listing all changesets of a repository, as well as a notification mechanism whenever a new changeset is known to the connector. (In reply to comment #1) > For a generic task-changeset connector, we would need an api for listing all > changesets of a repository, as well as a notification mechanism whenever a new > changeset is known to the connector. +1 It's good to have a general theme bugs but I would prefer if we opened separate bugs for specific enhancements. It keeps discussion focused and makes it easier to track changes in the SCM. Kilian, I have extended the API slightly since the last commit broke the Builds project. Can you take a look? I needed a way to retrieve a revision based for a resource that is not the latest workspace revision. Looks good for me. I'll import the builds project in order to get noticed when I'm breaking stuff. Anything pending on this issue ? There are still four open subtasks. We generally keep discussion tasks open until the topic is no longer relevant or all subtasks are resolved. 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 |