This is one of two issues introduced by changes in SF's security management: It now requires strong encryption. The solution proposed by Yuval Barness is correct.
The second issue is that SF has a new certificate which is not considered trustworthy by older Java versions. You need a JDK 8 minor version >= 101 to make Eclipse Update work with SF sites.
If there was a failure in a previous installation attempt, you might also need to delete and re-establish the update site under "Available Software Sites".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you, Tilman! I can finally check for updates of the Eclipse Tomcat Plugin again.
But this is quite a problem for those who aren't aware of the situation. While many people may keep up with installing the latest Java, many others do not. And some are forced by their workplace dev environments to use older versions. But even those who are dilligent about upgrading their JDKs will not know about the requirement of installing the required Java Cryptography Extension. I fear this will drive users away from Eclipse Tomcat Plugin out of frustration over installation problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course, some people won't be able to switch to a sufficiently recent Java version.
But you can always download the zipped updatesite under the tab "Files" and clicking on the link "Download update site archive (1.5 MB)". Then install it manually in Eclipse via Help > "Install new software..." > Button "Add..." > Button "Archive..."
There is also a copy of the project on Github (https://github.com/his-eg/tomcatplugin), but there are no releases available yet. Maybe somebody (Markus?) could create one...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, and that's what I did to get the latest version after encountering the update error for so long. But many users get their plugins from the "Eclipse Marketplace", and when they run into this issue, they may decide that the plugin is no longer supported. I have to admit, after this issue continued for so long, I was starting to believe that the maintainers had abandoned it because (I thought) surely they wouldn't let an update site issue continue this long if they were still involved with it. Anyway, it might be worth considering moving the update site to a different hosting service if SF is going to work this way.
And thanks again for clearly explaining how to resolve the issue on the user's end.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using Neon. Updated my JDK to 1.8.0_131 ... and I tried the security update listed above. No joy. So tried downloading the zip & exploded it, then tried to manually import. Tried the content.jar, tried the artifacts.jar, then even tried the .zip file. Each time Eclipse came back and told me "Unable to read repository at ....!/content.xml" I'm dying here. Would someone tell SF & Tomcat to fix this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it works for me, thank you, Yuval Barness,
I user spring tool with jdk1.8, when I install tomcat plugin, it will popup can not connect the repository, I have replace local_policy.jar and US_export_policy.jar which under %JAVA_HOME%\jre\lib\security, restart spring tools reinstall tomcat plugin successfully.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same issue. Running Eclipse SDK Mars.2 (4.5.2) on Windows 10 Pro.
after two days of struggling:
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
replace those two with the ones in %JAVA_HOME%/lib/security
and you'll be able to install after eclipse restart
Works for me, thanks.
This is one of two issues introduced by changes in SF's security management: It now requires strong encryption. The solution proposed by Yuval Barness is correct.
The second issue is that SF has a new certificate which is not considered trustworthy by older Java versions. You need a JDK 8 minor version >= 101 to make Eclipse Update work with SF sites.
If there was a failure in a previous installation attempt, you might also need to delete and re-establish the update site under "Available Software Sites".
Thank you, Tilman! I can finally check for updates of the Eclipse Tomcat Plugin again.
But this is quite a problem for those who aren't aware of the situation. While many people may keep up with installing the latest Java, many others do not. And some are forced by their workplace dev environments to use older versions. But even those who are dilligent about upgrading their JDKs will not know about the requirement of installing the required Java Cryptography Extension. I fear this will drive users away from Eclipse Tomcat Plugin out of frustration over installation problems.
Of course, some people won't be able to switch to a sufficiently recent Java version.
But you can always download the zipped updatesite under the tab "Files" and clicking on the link "Download update site archive (1.5 MB)". Then install it manually in Eclipse via Help > "Install new software..." > Button "Add..." > Button "Archive..."
There is also a copy of the project on Github (https://github.com/his-eg/tomcatplugin), but there are no releases available yet. Maybe somebody (Markus?) could create one...
Tilman wrote:
Yes, and that's what I did to get the latest version after encountering the update error for so long. But many users get their plugins from the "Eclipse Marketplace", and when they run into this issue, they may decide that the plugin is no longer supported. I have to admit, after this issue continued for so long, I was starting to believe that the maintainers had abandoned it because (I thought) surely they wouldn't let an update site issue continue this long if they were still involved with it. Anyway, it might be worth considering moving the update site to a different hosting service if SF is going to work this way.
And thanks again for clearly explaining how to resolve the issue on the user's end.
I'm using Neon. Updated my JDK to 1.8.0_131 ... and I tried the security update listed above. No joy. So tried downloading the zip & exploded it, then tried to manually import. Tried the content.jar, tried the artifacts.jar, then even tried the .zip file. Each time Eclipse came back and told me "Unable to read repository at ....!/content.xml" I'm dying here. Would someone tell SF & Tomcat to fix this issue.
Hi Eric, are you sure that your Eclipse is started with that JDK? Please check that in installation details.
Just checked: "Let's Encrypt" certificates are accepted by Java 7 >= 7u111, too (see https://letsencrypt.org/docs/certificate-compatibility/)
I finally managed to get the plugin installed using https://raw.githubusercontent.com/his-eg/tomcatplugin/master/net.sf.eclipse.tomcat.updatesite/ as updatesite. This should give me the lastest (unstable) version of the plugin, and should at least keep track of updates. Don't know, if this is could be a proper solution...
it works for me, thank you, Yuval Barness,
I user spring tool with jdk1.8, when I install tomcat plugin, it will popup can not connect the repository, I have replace local_policy.jar and US_export_policy.jar which under %JAVA_HOME%\jre\lib\security, restart spring tools reinstall tomcat plugin successfully.
The updatesite was moved to https://devtools.his.de/tomcatplugin/updatesite/ and the market place link was updated.