11-03-2009 05:10 PM
I receive this message:
An error occurred while collecting items to be installed
Error closing the output stream for net.rim.browser.tools.mdscs.feature220.127.116.11904091
Error unzipping C:\DOCUME~1\BBonner\LOCALS~1\Temp\net.rim.browser.
I installed JDK 1.6 U16 and also changed Eclipse -vm parameter to use the JDK at startup.
How do I finish installing this code? Thanks.
11-03-2009 10:15 PM
Can you list the following:
- Your operating system (XP/Vista and 32/64bit)
- Your version of Eclipse
- Which install you are trying (update site, full install, download zip file)
This should help us diagnose your issue.
11-04-2009 03:09 PM
We have seen from time to time that when our secure server is too busy it would simply drop the connection while downloading these .jar files from the update site.
Eclipse doesn't really give any feedback to the user that this has happened. The result is that the complete .jar file is not downloaded, but instead only some bytes of it. This causes the archive to become corrupt (files incompletely downloaded).
Unfortunately the workaround is to try to download the jars again from the update site.
11-05-2009 08:31 AM
Hi, thanks for the response. If that is really the reason -- why doesn't RIM put the jar files in a location that has adequate bandwidth like Amazon EC2/S3. I've never had this problem with any other eclipse plugins and I've been using it for quite some time. This might have been acceptable in the past, but with iPhone and Android phones out in the marketplace. I think you'll need to step up the game.
I'll also add that no other eclipse plugins I have installed prompt for authentication when installing. Most of them use a key after the fact -- perhaps you should try this route.
I'll try again.
11-05-2009 09:13 AM
We have been addressing bandwidth with our download site and we are making progress there. The download prompt has been put in place for legal and export controls reasons. The combination of these prompts and SSL can aggravate the problem you have experienced. We are also working with the internal teams to address this as well.
It is definitely a top priority for delivering our tools to the community.