Spring Tools 4 (aka Spring Tool Suite 4)

Probably related to this? https://stackoverflow.com/questions/21076179/pkix-path-building-failed-… ?

This is a known issue when running Eclipse on a JDK 1.8 and we are working on it. For a quick solution, run Eclipse itself using a JDK11, that should make the entries appear.

This is a known issue when running Eclipse on a JDK 1.8 and we are working on it. For a quick solution, run Eclipse itself using a JDK11, that should make the entries appear.

This is a known issue when running Eclipse on a JDK 1.8 and we are working on it. For a quick solution, run Eclipse itself using a JDK11, that should make the entries appear.

This might be related to an issue that I am investigating at the moment again. Are you running your Eclipse 2019-06 on JDK8? If so, could you try to run your Eclipse install with a JDK11 and a "-clean" option at least once to see if that changes anything? Another option to dianose the issue would be to open the "Console" view, switch to the "Host OSGi Console" and type "ss" for "short status". If there are certain STS bundles in the "INSTALLED" state, it might indeed be the issue that I am looking at right now and running with JDK11 should solve the issue. Another workaround would be to download a ready-to-use STS4 distribution from https://spring.io/tools, it works on JDK8 and JDK11 and comes on top of Eclipse 2019-06 with pre-installed STS4 components.

The URL that you mention (wih the "context.xml") doesn't exist indeed, but usually the update mechanism tries to access that and then tries the next variant, like the "compositeContent.xml" one. Maybe there is a proxy server in between that causes p2 not to recognize that this URL doesn't exist? What happens if you try "https://download.springsource.com/release/TOOLS/sts4/update/e4.11/" from the "Install New Software" dialog? Anything showing up?

In case the https protocol causes trouble (due to some network restrictions), you could also try the http variant (even though we don't recommend that), but maybe it helps in your situation at least.

We tried to switch the repo URLs to https instead of http, but there seems to be some hurdles along they way. We are on it. For the meantime, I switched the marketplace entries back to use http. Caches might take a while to update to that, but after that, you should be able to install again. You can also download a ready-to-use distribution from https://spring.io/tools, which is Eclipse 2018-12 with Spring Tools 4 pre-installed.

Yes, our switch to https caused some hiccups, I am sorry for that. I updated the marketplace entries, they should use the http p2 repo URLs again for installs, but you might have to wait a bit before caches are being updated. Another option would be to install the ready-to-use distribution from https://spring.io/tools.

We updated the bouncycastle bundles that we use for the Spring Tools 4 to the same versions that are shipped in Orbit (and the main Eclipse distribution), so this should be fixed with the recent version 4.1.2.

Yes, that is correct, the Spring Tools 4 don't ship the old Spring Config Editor for Spring XML Config files anymore. More details can be found here: https://github.com/spring-projects/sts4/issues/108

Yes, you can proceed. We are grabbing an unsigned snapshot version of those plugins for the latest version of the Spring Tools 4 and hope to be able to go back to signed versions for the next version. Until then, you can proceed and install those unsigned bundles.

Yes, you can proceed. We are grabbing an unsigned snapshot version of those plugins for the latest version of the Spring Tools 4 and hope to be able to go back to signed versions for the next version. Until then, you can proceed and install those unsigned bundles.

Yeah, Cloudflare caches the content for us, so that is fine, but the capture is strange and should not happen. But the URL is not meant to be used in a browser, so not sure where the capture appears...?!?

I would recommend to remove the update site URL from the preferences, restart STS, and try again. If that doesn't help, you could also try to go to "Install New Software" yourself (in your Eclipse installation) and select the update site there to see if that works. You could also try to use a slightly different one (http://download.springsource.com/release/TOOLS/sts4/update/latest/ or http://dist.springsource.com/release/TOOLS/sts4/update/e4.9/) - as a third option to try.

This is usually caused by a network glitch and stale cached data afterwards. Please go to the "Preferences -> Install/Update -> Available Update Sites" and remove to corresponding update site from that list (not disable it but remove it completely). Then restart and retry. That should solve the issue.

Another option would be to go to https://spring.io/tools and download a ready-to-use distribution of Spring Tools 4 for Eclipse, it is based on the latest Eclipse 2018-09 release and comes with the Spring Tools 4 pre-installed.

Spring Tools 4 don't contain any Spring perspective anymore, the major elements got added to the regular Java perspective, since that is what most people use for daily Spring Boot app development. So if you open an existing workspace that had the Spring perspective open from STS3 with STS4, you should close that perspective and continue with the Java one instead.

Downloading an individual bundle is possible, but it doesn't really help much, since you can't easily install that into your Eclipse. What happens if you go to "Install New Software" and put the HTTPS version of the URL in there? Does that work?

I am not aware of any mechanism that replaces the HTTPS automatically with the HTTP one and I am sure that the P2 repository that contains this bundle is available via the HTTP as well as tne HTTPS version of the URL. So maybe some network specific settings/proxies in your environment?

You could also try and download the whole STS 3.9.5 update site for Eclipse 4.8 from here: https://spring.io/tools/sts/all - and add that as a local update site to your installation (just an additional option to try).

The repository location hasn't changed, I guess there is an issue with stale data in the cache somewhere. You can go to the preferences, select the update location, and press "Reload", that usually helps. If not, remove the update site from the preferences, restart Eclipse, and add it back again (Preferences -> Install/Update -> Available Update Sites).

This looks like a typical network or repository caching issue. I would recommend to go to the Preferences -> Install/Update -> Available Updtae Sites, select the one that is used ("dist.springsource.com/release/TOOLS/update/e4.6" and/or "dist.springsource.com/release/TOOLS/update/3.9.2.RELEASE/e4.6/") and press "reload". That refreshes the internal repository caches. Then try again the install. You could also delete all those STS-related update sites from that preference and try again the marketplace entry. That should solve the issue.

Not sure how exactly you are trying to install the Spring Roo support (and why) and from which update site, but using the STS product update site from here (http://dist.springsource.com/release/TOOLS/update/e4.7/) should work. Otherwise I would recommend to download a ready-to-use STS distribution from that site and use the Dashboard to install the Spring IDE Roo extension from there.

MIght be a corrupted download or stale cache data in the p2 pool. I would suggest to delete the file, open Eclipse again, check the preferences if the STS update site already landed there and if so, select it and press "reload", just to make sure caches are invalidated. Then try again. Another option would be to use the update site directly or download a ready-to-use Eclipse distribution with the STS tools pre-installed via https://spring.io/tools.

In case you select Gradle as the build environment when importing or creating new Spring projects, you need to have some kind of Gradle support installed in your Eclipse environment. We strongly recommend to use Buildship 2 for this. The error message indicates that you probably don't have that support installed.

You can get Buildship from the Eclipse Marketplace (right from within Eclipse using the Help menu). Once you have that installed and select Gradle in the import wizard, the error should not appear anymore.

The mentioned artifacts are available, so it looks like there is some stale cache data somewhere. I would recommend to go to the Preferences -> install/Update -> Available Update Sites, select the one for STS (or multiple ones if you have more than one), and press "Reload". That should cause the cached data to be refreshed.

If this doesn't help, you could try to remove the update site from that list (in the preferences), restart Eclipse, and add it back to that list.

Hope this helps!!!