使用可用的Eclipse Mylyn支持git的分布式问题跟踪器？ [英] Distributed issue tracker for git with usable Eclipse Mylyn support?
问题描述
我正在使用 git 进行版本控制，但目前我缺少使用Eclipse Mylyn集成的问题/错误/故障单追踪器。
I'm using git for version control but I'm currently lacking a good issue/bug/ticket tracker with Eclipse Mylyn integration.
我正在寻找的功能：
- 开源实现以便我以后可以添加我需要的功能，GPL，LGPL，MIT或BSD许可证是首选）
- 分布式 存储在git存储库中，我打开了关于在与代码相同或不同的分支存储问题的跟踪器的建议）。
- 必须有 Eclipse Mylyn 支持（所以我可以通过mylyn界面打开和关闭问题，我认为一个明智的实现可以在特定端口提供本地HTTP服务器，而mylyn将使用Web模板连接器与问题跟踪器进行通话） 。最好在我切换分支机构时，Mylyn会自动查看开启和关闭的问题，但我可以这样做不那么聪明。
- 能够跟踪分支机构之间的问题示例：
- 我有一个共享父提交Z的分支X和Y。
- 提交Z有一个打开
- 分支机构Y有一个修复（提交Y4）并关闭Y中的问题。
- 分支机构Y有一个新的问题提交Y2）
- 分支Y合并在X中。
- 问题跟踪器会自动知道Z1在X中已修复，但现在有一个
- Open source implementation (so that I can add the features I need in the future. GPL, LGPL, MIT or BSD license preferred).
- Distributed (the issues must be stored in git the repository, I'm open for suggestions for trackers that store issues in the same or separate branch to the code).
- Must have Eclipse Mylyn support (so that I can open and close issues through mylyn interface, I think a sensible implementation could provide a localhost HTTP server in a specific port and mylyn would use "web template" connector to speak with the issue tracker). Preferably the Mylyn would automatically see issues opening and closing as I switch branches but I'm okay with this being less smart.
- Able to track issues between branches, example:
- I have branches X and Y with a common parent commit Z.
- the commit Z has an open issue Z1.
- the branch Y has a fix (commit Y4) and closes the issue in Y.
- the branch Y has a new issue (commit Y2)
- the branch Y is merged in X.
- the issue tracker automatically knows that the issue Z1 is fixed in X but there's now a new issue from commit Y2.
次要功能（会很好，但我可以没有生活）：
Secondary features (would be nice but I can live without):
- 小到足以包含在项目的源代码中：最好是具有可执行位集的单个文件（例如一个单一的bash或python脚本，完全实现）
- 某种Web用户界面，使没有Eclipse Mylyn的人至少可以添加新问题，并向现有的添加评论（不需要
您可以建议任何吗？
更新：截至2012-09-13，没有找到合适的工具。总结最好的比赛到目前为止：
Update: As of 2012-09-13 no suitable tool has been found. Summary of the best matches this far:
- Bug无处不在 - 没有Mylyn支持，在过去两年的Plannet功能中，Adrian Wilkins希望看到一个Mylyn连接器的状态。否则项目将继续进行。
- git-issues - 这个项目似乎已经死了。原作者大约在两年前停止了提交，其他作者在过去两年已经做了不到十次的作品。
- git-case - 这个项目似乎已经死了。原作者三年前停止提交。
- stick - 这个项目似乎已经死了。我甚至找不到公共资料库。
- TicGit
- TigGit -NG - 这个项目似乎已经多次死亡，但到目前为止，有人一直都是采用该项目。没有Mylyn也支持这里。需要最近的Ruby环境才能运行。
- TicGit.net - 这个项目似乎是以C＃编写的TicGit的win32 / .Net特定分支。不符合我的需要。
- Bugs Everywhere - no Mylyn support, the status has been "Adrian Wilkins would like to see a Mylyn connector for BE" in the "Plannet features" for the last two years. Otherwise the project keeps going.
- git-issues - this project seems to be dead. Original author stopped making commits about two years ago and other authors have done less than ten commits in about last two years.
- git-case - this project seems to be dead. The original author stopped making commits three years ago.
- stick - this project seems to be dead. I couldn't even find public repository anymore.
- TicGit this project seems to be dead. All repositories I could find have disclaimer that the project is no longer developed.
- TigGit-NG - this projects seems to have died multiple times but this far, somebody has always adopted the project again. No Mylyn support here either. Requires pretty recent Ruby environment to run.
- TicGit.net - this project seems to be win32/.Net specific fork of TicGit written in C#. Does not match my needs.
推荐答案
你可以看看 GitIssues ，它与git命令行很好地集成在一起。可悲的是，它不支持Mylyn。然而，创建Mylyn连接器应该很容易，因为它可以导出到XML。
You could have a look at GitIssues which is well integrated with the git command line. But sadly, it doesn't support Mylyn. Nevertheless it should be easy to create a Mylyn connector since it can export to XML.
你可以看看这个列出分布式错误跟踪系统。
这篇关于使用可用的Eclipse Mylyn支持git的分布式问题跟踪器？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
