用于 Sourceforge 功能/错误跟踪系统的 Mylyn 连接器
我还没有找到任何关于这方面的明确信息。
是否可以将 sourceforge 的错误/功能跟踪系统与 Mylyn 集成?
我发现 this 页面看起来有点旧(实际上,用于下载通用连接器的链接不起作用)。
有人对此有任何线索吗?这样的连接有可能实现吗?
I haven't found any clear information about this around.
Is it possible to integrate the sourceforge tracking system for bugs/features with Mylyn?
I've found this page that seems a bit old (indeed the link for downloading the general connector does not work).
Anyone have a clue about this? It is possible to realise such a kind of connection?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
是的,随着 SourceForge 转向使用 Allura,您突出显示的页面上的配置已过时。
我在 上发布了有关让 Web 模板连接器适用于 Allura 的详细信息http://officefloor.wordpress.com/2012/12/10/allura-sourceforge-mylyn-connector/
Yes with the move of SourceForge to use Allura the configuration on the page you highlighted is outdated.
I posted details on getting the Web Template Connector to work for Allura at http://officefloor.wordpress.com/2012/12/10/allura-sourceforge-mylyn-connector/
通用连接器现在位于 Mylyn 培养箱中。使用此下载站点:
http://download.eclipse.org/mylyn/incubator/3.7(适用于 Eclipse 3.6 , 3.7, 3.8)
The generic connector is now in the Mylyn incubator. Use this download site:
http://download.eclipse.org/mylyn/incubator/3.7 (for Eclipse 3.6, 3.7, 3.8)
由于我无法让它运行 – 也许是因为 Eclipse Luna 或其他原因 – 我稍微修改了 Daniel 的方法,部分使用 REST 接口:
基本配置
${serverUrl}/p/${project}/${tickets}/
(与 Daniel 的方法相同)${serverUrl}/p/${project}/${tickets}/new
(与 Daniel 的方法相同)${serverUrl}/rest/p/${project}/${tickets}?access_token=${bearer_token}
\{"summary":\s*"({Description}.+?)",\s*"ticket_num":\s*({Id} .+?)\}
里程碑查询
要按里程碑查询任务,请使用以下命令参数在您的编辑查询配置中:
${serverUrl}/rest/p/${project}/${tickets}/search?q=_milestone%3A${milestone}&access_token=${bearer_token}
Since I wasn't able to get it running – maybe it's because of Eclipse Luna or something else – I slightly modified Daniel's method which partially uses the REST interface:
Basic Configuration
${serverUrl}/p/${project}/${tickets}/
(the same as in Daniel's method)${serverUrl}/p/${project}/${tickets}/new
(the same as in Daniel's method)${serverUrl}/rest/p/${project}/${tickets}?access_token=${bearer_token}
\{"summary":\s*"({Description}.+?)",\s*"ticket_num":\s*({Id}.+?)\}
Milestone query
To query tasks by milestones, use the following parameters in your Edit Query configuration:
${serverUrl}/rest/p/${project}/${tickets}/search?q=_milestone%3A${milestone}&access_token=${bearer_token}