Installing the ADT Plugin for Eclipse

Question

I am trying to install the ADT plugin for Eclipse. However, after I have went to "Install New Software..." and entered the plugin location https://dl-ssl.google.com/android/eclipse/, "Pending..." is displayed. It does not change to "Developer Tools" no matter how long I wait. (I have also tried "http://dl-ssl.google.com/android/eclipse/)

To get around this I tried downloading the current ADT Plugin zip file, but this does not work either. "Developer Tools" appears, but when I click "Next" it does not move past "Calculating requirements and dependencies."

Please provide a solution to the problem of either approach. Thanks.

Solution 1

I had the same problem. It started working when I unchecked the box labeled "Contact all update sites during install to find required software".

Solution 2

1. Goto Preferences->Network Connections and set the correct option (native/direct as per your proxy settings on your network) restart eclipse and try again. [Switching to direct worked for me at home, however in office i had to configure it to native..] (Proxy settings require restart of eclipse IDE on some machines to take effect)
2. Ensure that your eclipse has all android toolkit dependencies (wst/emf...) installed (http://developer.android.com/resources/faq/troubleshooting.html#installeclipsecomponents)

Solution 3

Update

The logged error you provided leads to Install from updatesite hangs under Java 7 and in turn Eclipse Bug 362741 - downloads from update sites hang - (3.7.1 Indigo SR1 windows), see comment 6 specifically (you already applied comment 7).

Please note that while this seems to be a JDK 7 problem at first sight, the linked Java Bug 7077696 - java.net.Socket closes when "PASV" is sent on an authenticated FTP connection classifies the issue as a REGRESSION. Last worked in version 6u26, while you are using 6u30 already. Accordingly, the issue is reported to be fixable by switching to Java 6 elsewhere (implying an earlier version), see e.g. Cannot do any software installs using jdk1.7.0_01 (which uses 6u22):

However, everything works right if I then change the eclipse.ini to change the vm to JDK 1.6:

-vm C:\Java\jdk1.6.0_22\bin\javaw.exe

Oracle's Evaluation concludes, that This does not appear to be a JDK bug, rather it's just the Windows firewall recognizing and blocking the ftp protocol.:

The only difference between JDK7 and older releases is that the JDK is using IPv6 sockets when IPv6 is enabled and so IPv4-mapped IPv6 addresses are used. it may be that Windows or the firewall is not configured to allow IPv6 sockets. [...]

Accordingly, they list a Workaround as well:

Run with -Djava.net.preferIPv4Stack=true

• add a firewall exception for the Java binary.

• run with -Djava.net.preferIPv4Stack=true (which disables IPv6 and uses AF_INET sockets exclusively)

• or disable stateful FTP inspection in the firewall (registry setting or netsh command)

The firewall adjustment seems to be a confirmed workaround as per comment #4 in Socket Exception only in Java 7 (though simply turning it off like there should be handled with care of course).

Good luck!

---

Presumably you are already aware of Robamaton's answer to Eclipse, Android Plug-in, Install New Software just says “pending” (there are many ADT related questions and strangely it didn't show up immediately in a respective search)? It basically comes down to Codejammer's hint towards Preferences->Network Connections (+1), though with an explanation why it might still fail on your network regardless, see the comments:

Oh, I read that it doesn't respond to general requests from browsers. In any case, network admin confirms it's making a socks connection, but then doing nothing further.

and

Ok, further to previous comment, it's probably trying to connect via. socks 5 - but our network only has socks 4. Admin is going to run the 5 version to see if it then works.

Workaround

Regardless of whether the socks 4 vs. socks 5 proxy settings are actually the problem, a potential workaround might be to install Eclipse and ADT on a different system (ideally on a different network), and copy the resulting folder to yours thereafter (after all, an Eclipse installation is simply a collection of files).

When doing so, please ensure to match 32- vs. 64-bit regarding both the JDK and Eclipse between the source and the target system, because a mismatch would yield other problems (see e.g. my answer to Failed to load the JNI shared library on starting Eclipse).

Solution 4

If you were unable to get network update working, please try downloading the ADT zip package and installing locally as the download page says.

http://developer.android.com/sdk/eclipse-adt.html

Solution 5

I find these google sites very difficult to connect with from certain networks, but not from others. Here in Germany, I had terrible trouble going through Alice, but none going through Deutsche Telekom.

Sometimes I could reach the dl-ssl host from Alice, but in some later operation it would hang then time out. A day or so later, I might be able to make a connection again. Some people say they had luck going through a proxy, or by changing "http" to "https". I also saw this.

Here's what I think is going on.

First, Eclipse is miserably buggy, and handles unexpected situations very badly (for example, catching all exceptions, but failing to provide the exception's message!!), particularly when it comes to unresponsive links. It reminds me of the stock story of the mentally disturbed psychiatrist.

It looks as though the google server is badly configured, possibly as a naive protection mechanism meant to repel denial-of-service attacks: it only handles a few connection requests within a certain time frame from hosts certain networks, and if it gets too many requests, it locks out connections with the host for a long time.

Unfortunately, a single Eclipse update might require many connections in rapid succession; somebody unsure of how to configure Eclipse the first time will likely trip the Google booby-trap.

In my case, I was able to download what I needed by carefully choosing a subset of the available software, being very patient, and if I got locked out, just waiting a day until it let me in again.

Cheers!

View more solutions

Comments

[Greg Bacon]

Welcome to Stack Overflow! Your answer would have been better as a comment to the original question because it gives a hint but not a definitive answer.

[Greg Bacon]

I've tried changing the network preferences. I've tried 1.6 and 1.7_04 JDK. I've tried disabling all but the Indigo update site. I've tried setting Arrays.useLegacyMergeSort to true. I tried installing from a zip file. I've tried unchecking "Contact all update sites." In spite of all these attempts, none of the eclipse.org sites will proceed past "Pending..."

[Greg Bacon]

I'm seeing the problem on a home network connected to residential broadband. In the installer, if I select the URL for Google Plugin for Eclipse, http://dl.google.com/eclipse/plugin/3.7, Eclipse can fetch those packages, but the install fails because it needs to update an Eclipse package. All of the Eclipse install sites remain stuck in the pending state.

[Steffen Opel]

@Greg: Well, that's important information and yields a different picture accordingly - what Eclipse package needs to be updated by the install and fails? Have you tried running the install as an administrator already? Is this a fresh Indigo installation? Which error does the log report (see Where are Eclipse's log files located?)?

[Greg Bacon]

The missing prerequisite is org.eclipse.wst.css.core 0.0.0. Yes, I've tried running as an administrator. Yes, this is a fresh Indigo installation. The errors in the log are instances of SocketTimeoutException downstream of FileTransferJob.

[Greg Bacon]

Installation fails on a fresh Indigo installation even with JDK 6.

[Steffen Opel]

@Greg: I've updated the answer with insights gathered from the logs you provided; given all the details this explanation looks promising, hopefully the workaround applies for you as well!

[codejammer]

Have you tried directly unpacking the zip file into your eclipse directory instead of going through the install mechanism? You have to just put features in the features directory and plugins in plugins directory and launch eclipse with -clean

[Greg Bacon]

All the Available Software Sites use the HTTP protocol, not FTP. I added the IPv4 option to eclipse.ini and added an exception for eclipse.exe, but still no dice.

[Greg Bacon]

I'll be happy to try anything at this point! How do I fetch the zip files directly?

[Yury]

@Greg, I've also found that you use eclipse x64. As I understood from logs you have x64 computer architecture but winwows is 32 bit. So in this case you have to download JDK 6 32bit and also Eclipse 32bit. Have you tried this?

[Steffen Opel]

@Greg: sorry to hear - what protocol is actually used during the various stages of the apparently complex Eclipse update process cannot necessarily be deduced by the URL of the update site alone though, i.e. Eclipse may well switch to to other protocols on the fly (e.g. for the file listing); either way, I've found more hints that the referenced issue might be the problem still (see update), ... [continued]

[Steffen Opel]

[continued] ... so given the complex and meanwhile twisted test scenarios, I'd recommend to double check this, ideally by using an earlier JDK (e.g. 1.6.0_22, which resolved this here, or temporarily turning off the Windows firewall entirely for testing (which resolved this here), if feasible security wise. Other than that I'm running out of ideas here as well, sorry!

[Greg Bacon]

I double-checked, and Control Panel reports that I'm running 64-bit Windows.

[codejammer]

@GregBacon have you tried the zip from dl.google.com/android/ADT-16.0.1.zip yet?

[bad_keypoints]

Helped me too! Thank you very much!

[Ripon Al Wasim]

You can also try by using "Eclipse Marketplace" . Please follow my answer here: stackoverflow.com/questions/11445661/…