Eclipse mylyn连接器插件，包括已发布的更新网站上没有的补丁，可在。
我一直在圈子里四处乱逛，试图弄清楚如何在我的日食安装中安装并运行此操作，而无需成功。
任何帮助将不胜感激。
更新：，
如建议的，我可以从。我还可以使用Maven构建，并从生成的目标更新站点zip中安装。
但是，在这两种情况下，插件都表现得好像正在使用未拨打的版本一样。具体来说，当添加新任务存储库时，它会执行验证，该验证持续了很长时间（一个小时），并且失败了，错误约为50,000 API调用限制。 Wireshark显示了Gitlab.com的大量流量，每5秒钟一次流量。
如果我使用Eclipse PDE在调试Eclipce实例中测试插件，那么一切都按预期工作！
我意识到，这已经摆脱了原始话题。
An Eclipse Mylyn connector plugin, including a patch not available at the published update site, is available at https://github.com/teknodan/mylyn-gitlab.
I have been round and around in circles trying to work out how to get this installed and running in my Eclipse installation, without success.
Any help would be appreciated.
Update:
As suggested, I can install from https://raw.githubusercontent.com/teknodan/mylyn-gitlab/gh-pages/. I can also build using maven and install from the resulting target update-site zip.
However, in both cases, the plugin behaves as if it were using the unpatched version. Specifically, when adding a new task repo, it performs validation which goes on for a long time (an hour) and fails with an error about a 50,000 API call limit. Wireshark shows lots of traffic to gitlab.com, with one burst of traffic every 5 seconds.
If I use Eclipse PDE to test the plugins in a debug Eclipce instance then everything works as expected!
I realise that this has wandered off the original topic.
发布评论
评论（1）
正如 @greg-449和@howlger指出的那样，我需要做的是使用maven（
mvn package）自己构建它.gitlab.updatesite/target 。我不太确定为什么我必须碰到版本号（
2.2.0.qualifier）。我还必须将主pom.xml版本配置为2.2.0-snapshot和＆lt; parent＆gt;版本的儿童poms。如果我首先完成了MVN清洁，也许我可以少逃脱。但总而言之，它现在正在起作用。感谢所有。
As pointed out by @greg-449 and @howlger, what I needed to do was build it myself using maven (
mvn package) and then install using the site archive inde.weingardt.mylyn.gitlab.updatesite/target.I'm not quite sure why I had to bump the version numbers (to
2.2.0.qualifier). I also had to configure the mainpom.xmlversion as2.2.0-SNAPSHOTand the<parent>version for the child POMs. Perhaps I could have got away with less if I had done amvn cleanfirst.But all in all, it is now working. Thanks to all.