4

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

Maarten Baars
  • 71
  • 2
  • 4

2 Answers2

2

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.

Community
  • 1
  • 1
Michael Lowman
  • 3,000
  • 1
  • 20
  • 34
  • I am using Eclipse SDK 3.6.2 Build id: M20110210-1200, strange you're using a newer version. Could not find that one on the Eclipse site. Or don't you use the Classic version? Anyhow, switching to classic updates did not help. I did not try and install an older version of Eclipse. Maybe I will, but it seems strange to use older versions. I don't know what you mean by placing the plugin.zip into dropins folder. Where is the plugins.zip?! Hopefully it is possible to make it work. I'm really surprised it takes so much effort to just install some plugins... – Maarten Baars Jun 17 '11 at 18:44
  • nah, I usually use most recent stable versions of the next release off projects. Currently that's 3.7 RC4, and I'm at RC3, but I'll update to 3.7 as soon as it releases. I use [this](http://download.eclipse.org/eclipse/downloads/) as the base and add packages I want; I usually have Java SE, EE, CDT, PDT, and a few others. – Michael Lowman Jun 17 '11 at 18:48
  • By the way, where's the TRANSFER TAB? Dont see it. And I now use the same version as you. Does not work either. Maybe its my java virtual machine? Is that the wrong version? Any ideas how to check that? Just installed the latest version. – Maarten Baars Jun 17 '11 at 19:03
  • ah, it's the view that shows progress. In fact, it's called progress, not transfers at all. My mistake. Two terminology mistakes in one term. But it just lets you terminate transfers so you can see all of the files Eclipse tries to download, in order. – Michael Lowman Jun 17 '11 at 19:07
1

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.

rahul kumar
  • 11
  • 1