无法在 Eclipse 中安装更新或插件

发布于 2024-11-16 03:09:56 字数 452 浏览 5 评论 0原文

在工作中,我们使用 Adob​​e Coldfusion Builder,并且安装 MercurialEclipse 等插件没有问题。但在家里我想使用 Eclipse 本身,但遇到了很多很多问题。当我尝试联系 http://cbes.javaforge.com/update 时,它只是说“无法读取存储库位于 http://cbes.javaforge.com/update/content.jar。更新导致无休无止...待定...

阅读有关此问题的所有文章,也找不到我的解决方案。

这里出了什么问题?我以为是防火墙关闭了,但没有成功。尝试 的方向。

我走向正确 马丁

At work we use Adobe Coldfusion Builder and got no problem installing plugins like MercurialEclipse. But at home I would like to use Eclipse itself, but am running into many many problems. When I try to contact http://cbes.javaforge.com/update it just says "Unable to read repository at http://cbes.javaforge.com/update/content.jar. Installing updates result in an endless ...pending...

What is going wrong here? I thought it would be the firewall. Turned it off, no succes. Tried reading all the articles about this problem, could not find my solution there as well.

Hopefully someone can pinpoint me to the right direction.

Thanx!!
Maarten

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

城歌 2024-11-23 03:09:56

您使用的是不同版本的 Eclipse 吗?尝试在更新之前打开传输选项卡,看看它是否阻止下载 content.jar 等内容。如果是这样,问题在于存储库仅支持经典更新站点,而 Eclipse 仅使用 p2。

至于解决这个问题...我注意到这在最新版本的 Eclipse 上不起作用。根据文档,经典仍然应该受到支持。我不知道这是行为的改变还是错误。解决方法可能是使用较旧的 Eclipse,切换到首选项、常规/功能中的经典更新,或者可能将插件的 zip 放在 eclipse dropins 文件夹 (eclipse/dropins) 中。

我还没有尝试过这些,但首选项似乎最有可能。

我正在使用 Eclipse 3.7 版本 I20110526-1708。

编辑

是的,你可以看出这是一个p2问题: http://cbes.javaforge.com/ update/content.jar 是 404,而 http://cbes.javaforge.com/update/site.xml 工作正常。 site.xml 是经典的更新机制。

根据 wiki

但是,用户很少需要启用 Update Manager,因为 p2 可以从专为 Update Manager 设计的任何更新站点进行安装。

我刚刚亲自尝试过,并且可以验证 Capabilites 解决方法是否有效:启用它后,转到“帮助”>“软件更新”>“查找并安装”。单击搜索要安装的新功能,并将您的站点添加为远程站点。

它应该成功找到提供的功能。

正如 wiki 上所列出的,这是一种解决方法,通常不应使用。我不知道为什么有必要;我自己找不到相关信息。

至于dropins目录,我犯了一个错误:它应该是一个jar文件,而不是一个zip文件。 插件的 jar,可以通过查看site.xml 文件。不过,这可能是比第一个更糟糕的解决方法。

Are you using a different version of Eclipse? Try opening the transfers tab before you update and seeing if it's blocking on something like downloading content.jar. If so, the problem is that the repository only supports classic update sites, while Eclipse is only using p2.

As to solving it... I noticed this wasn't working on very recent builds of Eclipse. According to docs, classic is still supposed to be supported. I don't know if this is a change in behavior or a bug. Workarounds would probably be using an older Eclipse, switching to classic updates in Preferences, General/Capabilities, or possibly placing the plugin's zip in the eclipse dropins folder (eclipse/dropins).

I haven't tried these, but the Preferences seems most likely.

I'm using Eclipse 3.7 build I20110526-1708.

Edited

Yeah, you can tell that it's a p2 problem: http://cbes.javaforge.com/update/content.jar is a 404, while http://cbes.javaforge.com/update/site.xml works fine. site.xml is the classic update mechanism.

According to the wiki:

However, users will rarely have a need for enabling Update Manager, because p2 is able to install from any update site that was designed for Update Manager.

I just tried this out myself, and can verify the Capabilites workaround works: After enabling it, go to Help>Software Updates>Find and Install. Click Search for new Features to install, and add your site as a remote site.

It should successfully find the provided features.

As listed on the wiki, this is a workaround, and shouldn't normally be used. I'm not sure why it's necessary; I couldn't find information about it myself.

As for the dropins dir, I made a mistake: it should be a jar file, not a zip. The plugin's jar, which can be found by looking through the site.xml file. This is probably a worse workaround than the first, though.

忘东忘西忘不掉你 2024-11-23 03:09:56

这可能是与代理相关的问题。转至网络连接首选项页面并在活动提供商中选择手动。然后选择 HTTP,单击“编辑”,然后提供必要的详细信息。在首选项页面中对 HTTPS 执行相同的操作。然后关闭首选项页面并重试。它应该有效。

It may be proxy related issue. Go to network connections preference page and in active provider select manual. Then select HTTP, click on edit and then provide the necessary details. Do the same for HTTPS also in the preference page. Then close the preference page and try again. It should work.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文