I've just installed Eclipse Luna v4.4.0 and trying to access marketplace.
During load Eclipse fails, reports nothing to stderr and terminates.
I'm using no proxy if that means.
Does anybody met any bug like that?
There are some bugs with Eclipse Luna and the Marketplace Client. You should follow the instructions here to get the fixed version.
https://www.eclipse.org/mpc/
I found a solution somewhere (it works with Luna and Mars too):
Add line:
org.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient4
into
<your eclipse folder>/configuration/config.ini
And restart eclipse.
This is a known bug for Eclipse LUNA.
bug-422665
But htere is a work around.
Go to eclipse Luna installed folder/Plugin/
take backupo of this two below files
org.eclipse.ecf.provider.filetransfer.httpclient4.ssl_1.0.0.v20141221-2352.jar
org.eclipse.ecf.provider.filetransfer.httpclient4_1.0.1043.v20141221-2352.jar
Copy corresponding two files form eclipse-Kipler/Plugin folder if you have already installed it. or can search online.
org.eclipse.ecf.provider.filetransfer.httpclient4.ssl_1.0.0.v20130604-1622.jar
org.eclipse.ecf.provider.filetransfer.httpclient4_1.0.300.v20130604-1622.jar
Start Eclipse now.
Worked for me and many others. THis is just a work around and not a permanent solution.
Hope this Helps.
Related
I downloaded the latest adt bundle (adt-bundle-windows-x86_64-20140624), and uncompresed that zip file, but when i try to open that adt, it open as juno eclipse. can any body help me to resolve this prblem.
thanks in advance
ADT Bundle contains Eclipse, to start Android development you need the ADT and the bundle comes with both you don't have to spend time searching for the ADT and Eclipse
Same problem here, using OSX. The downloaded ADB dows not show the typical ADB buttons and other extension provided by the plugins, but just a plain Eclipse. Installing an older version of ADT (adt-bundle-mac-x86_64-20140321) and updating won't help.
The package seemes somehow broken, some files like the ADT app icon, just aren't there. Other people experimented problems (Same problem; Other problem, also documented here).
I know it's not a real answer, but I just switched to Android Studio. I think the only other option is reverting to an older versione and wait for a new release.
To not get blocked I've continued to install the latest ADT Bundle 23.0.0 and adt-bundle-windows-x86_64-20140624 fresh on my system. Updated the SDK to the latest and continued to set "targetVersion as '19'" instead of setting it to 20 or 21.
That way you can proceed ahead with your coding and later when things get resolved...you can implement that to new version. BTW, I've also selected 'Blank Activity / Empty Activity" during the project creation
Comment back if it makes sense or NOT until the problem gets resolved by Google... :)
The Bug thread about this issue can be tracked here : Latest ADT Bundle Bug Tracker
I've installed Eclipse 4.2 Juno. Now I want to install aptana for developing ruby, but I get the following error,
Unable to read repository at http://download.aptana.com/studio3/plugin/install/content.jar.
Unable to read repository at http://download.aptana.com/studio3/plugin/install/content.jar.
Read timed out
I assume that by now you have probably solved the problem, but I had exactly the same problem and found the solution after many searches, so for the sake of any others searching here...
The URL you need to enter in the 'Install New Software' dialog is
http://download.aptana.com/studio3/plugin/install
The following answer was correct. I just tested it with Eclipse Juno.
Steps:
Open Eclipse
Help -> Install New Software
Add (on the top right)
Enter the following link for Aptana Plugin with Eclipse Juno: http://download.aptana.com/studio3/plugin/install
Click OK
Put a check mark for Aptana Studio 3
Next -> Next -> Finish
download.aptana.com/studio3/plugin/install did not work for me. I am using Eclipse 4.3 based STS 3.4
Instead I got the appropriate update site link from this site Aptana Update Site
This is the link for Eclipse plugin update site http://d1iwq2e2xrohf.cloudfront.net/tools/studio/plugin/install/studio3/3.4.2.201308081736/
There is also a link to download the plugin and install through archive. I have used the above update site link and no problem at all.
Hope that will help others.
Adding this answer in case somebody still gets this error while using the correct URL from JonB's answer (http://download.aptana.com/studio3/plugin/install )
Restart Eclipse and try again.
This appears to be a transient issue, as mentioned here:
Aptana studio 3 cannot contact download.ecplise.org
It worked for me after a retry.
I also gone through same problem. But Following solution works for me,
In Eclipse, go to "Eclipse Marketplace" and search for Aptana 3 and hit the Install button.
Help -> Eclipse MarketPlace
Eclipse Market place - Aptana 3 Studio plugin
I wondered myself whether to install the standalone or the plugin. I tried the plugin based on aptanaès instructions and it failed on the first try.
As usual SO respondents reported this problem.
I restarted Eclipse, and then did the install with Aptanaès URL
http://download.aptana.com/studio3/plugin/install
and it worked.
My environment was Eclipse JUNO,
As of 01/29/18 and Eclipse Photon, none of the URLs listed as answers here work in Eclipse's built-in software sources panel. However, after some trial and error mashing up Aptana's old download URLs with the ones Appcelerator (which bought Aptana in 2015) uses for its own software, I got:
http://download.appcelerator.com/aptana/studio3/plugin/update/stable
This works, is totally plug-and-play, and is obviously official - no need to go off to some shady 3rd party hosting site. I just wish someone at Appcelerator had spent 15 minutes to post it somewhere.
This question is more of type "has anyone experienced something similar before and if so, what was the issue?".
At work I use an iMac to do my daily programming. After some initial (and still occasional) struggles, I got my project running on Virgo server. Stand-alone or from Eclipse, both work.
I checked out the same code at home on my Windows PC, installed same version of Eclipse and Virgo. I took the same installation & configuration steps like on the Mac at work. I can get the project up & running stand-alone. However, when I try to get the project deployed from withing Eclipse, no matter what I try, some bundles would not deploy.
As one of desperate last options I even moved Virgo to a c:\v, just in case the path was to long. Still no success.
Did anyone experience something like this before? What was the reason? Any hidden configuration I might be missing?
Thanks,
Jan
you can have a look at the Virgo\work\org.eclipse.virgo.kernel.deployer_<someVersion>\staging\global\bundle\ directory. Virgo tooling should normally deploy to this directory and invoke the deployer. maybe there are some issues. i suppose, you already checked the debug-output-logs? maybe it issnt a problem of deployment but something else.
Has anyone successfully installed and run the Blackberry Eclipse plugin for MacOS?
Apparently, BB has not improved their Mac support much in the last year, since there was a question here about it last year.
I've followed their instructions to the letter, but they seem to assume that all you'll ever do in Eclipse is use their plugin. I want to move their plugin into an existing Eclipse installation.
I've copied the net.rim.* files from their Eclipse installation in to my /plugins folder, restarted, they show up in the list of installed plugins, but building an app always yields this error:
"Failed importing native project for BlackBerry. Missing Blackberry plugin. For more details see http://na.blackberry.com/eng/developers/javaappdev/javaupdate.jsp"
Thanks.
Mike
Here's the secret:
point Eclipse 3.6 Hellios to the following plug-in URL: http://www.blackberry.com/go/eclipseUpdate/3.6/web
Eclipse/Help/Install New Software... Add, enter some name and the URL above, and it works.
Today I had a problem with my old Eclipse 3.4 installation and I had to re-download the entire package. However, I don't think that I got the exact package as before, and I'm having some problems.
The problem can be summarized as follows: when developing a plug-in, I cannot resolve dependencies towards 'org.eclipse.jdt.ui'. When trying to add the missing plugin, in the dialog the closest match is 'org.eclipse.jdt.ui**.source**'. A similar thing happens with other core plugins.
In order to test, I created a new plug-in using the wizard and I obtained a non-compiling plugin: one of the classes uses the class org.eclipse.jdt.ui.JavaUI and it cannot be resolved. Similarly, the MANIFEST.MF includes a dependency towards 'org.eclipse.jdt.ui', but the 'Bundle 'org.eclipse.jdt.ui' cannot be resolved'.
Now a summary of my platform:
I'm running Mac OS X 10.4 Tiger and Java 1.5.0_19-138
I'm running Eclipse Version: 3.4.1 Build id: M20080911-1700
I downloaded the modeling package, which comes in a file called 'eclipse-modeling-ganymede-SR1-incubation-macosx-carbon.tar.gz'
I've performed a fresh installation, in a new folder and using a new workspace.
If I look at the Plug-in Registry view, I can find the 'org.eclipse.jdt.ui' plugin in there, and it appears to be running. By the way, if it is disabled, then the workbench breaks and stops working.
I cannot understand what is happening. Is my installation broken? I wonder if the Eclipse package that I downloaded has an error and they included the sources instead of the compiled files. But in that case, the plug-in shouldn't be working in the workbench, isn't it?
In any case, why I cannot find the plug-in when I'm adding the dependencies, even if I see it in the Plug-in Registry?
Thanks for your help!
Problem solved: just restart the computer.
I don't restart my computer very frequently, so it took me a lot of time to find out that this was the solution. After I restarted it, everything started to work perfectly again. It seems that either Eclipse leaves something in the memory after running, or that some of my initial failures had left something nasty behind. In any case, I had checked and there were no Eclipse related processes running .... weird, but at least now it's fixed!