Eclipse Che is supporting VS Code extensions in its IDE.
Each workspace can have its own set of plug-ins. This definition of plug-ins is stored inside a
devfile.yamlfile containing as well the list of projects to clone.
From the dashboard, there is a list of plug-ins that can be enabled on a given workspace.
When a plug-in is enabled, a new entry is added in the
For example, enabling AsciiDoc plug-in is adding the following snippet in my devfile.
Eclipse Che has many thousands of users. Most of them use the VS Code-inspired browser IDE, but sometimes you know you’re going to be offline for awhile and want to be able to work with a local editor, then sync back your changes when you’re back online.
Obviously if you only care about changes to the source code then git will handle this just fine. But if you want to run it offline, make changes to your tools, runtimes or dependencies then it’s great to be able to have all that synced back to Eclipse Che.
In this article we’ll…
Eclipse Che is a Kubernetes-Native IDE. It might be interesting to work on your project using remote resources instead of consuming your laptop resources. Another interesting way is to use containers that might be used in production as well.
Also let say you’re running out of battery, you may spare CPU and get extra time !
In this article we’ll cover how to set this up, by:
In a previous blog post, we’ve experimented ready-to-use workspaces and how to write/run/debug code easily.
But when we are open a ready-to-use workspace, it seems that there is some magic:
In this blog post, we’ll discover what drives this workspace magic: the devfile.
A devfile defines the configuration of the workspace, which is the developer’s environment. This definition is portable - we can create…
Eclipse Che 7 has been announced few days ago, if you have not yet tried it, it’s time to experiment with all the new exciting capabilities!
This guide will drive you through different steps and allow you to experiment Che 7. To follow this guide, you’ll not need to install Che on your machine or your K8S cluster, we’ll just be using a free online instance of Eclipse Che that is running at https://che.openshift.io
It’s a free-to-use instance that is powered by latest Eclipse Che 7 version and providing 3GB of memory for a single workspace. …
Over the last month, the Eclipse Che community has been adopting Eclipse Theia as the default web IDE provided with Che developer workspaces. We’ve enriched the Eclipse Theia with a plug-in model to provide VS Code extension compatibility. This blog post explain why we decided to add the plug-in model to Eclipse Theia and what are the benefits when it’s used with Eclipse Che developer workspaces .
In Eclipse Che 6, it is possible to develop and plug-ins on top of the GWT IDE but it is not possible to load them at runtime without stopping/recompiling and then reloading the…
Docker Desktop on macOS (and on windows) is embedding Kubernetes since several releases.
Kubernetes being a standard of deploying cloud applications, let’s try to use this embedded Kubernetes directly provided by Docker Desktop instead of using another Kubernetes installation like by installing minikube.
First, check that a recent version of Docker Desktop is installed. Click on the whale in status bar and click on
About Docker menu.
In this blog post, we’ll demonstrate how to use the serverless capabilities of Apache OpenWhisk by writing actions within Eclipse Che.
There are several ways to deploy Apache OpenWhisk. I’ve followed the MiniShift setup which deploys both Eclipse Che and Apache OpenWhisk on top of MiniShift. It’s easy to setup and to reproduce.
Here is the installation guide for Apache OpenWhisk on MiniShift
Note: do not forget to launch this command after MiniShift startup (else pods won’t start correctly)
$ minishift ssh -- sudo ip link set docker0 promisc on
We can check OpenWhisk is running by using the following…
In the first post, I described what needed to be done to make Che workspaces run Java 9 (which means getting the Che server to run Java 9 too).
Now I want to explain what had to be done so contributors to the Che project could compile and run with Java 9.
The latest Eclipse Che stable release (v5) was designed and built on top of Java 8. So when a new version of the JDK, Java 9, was released we had to ensure that Eclipse Che could be built and run on top of Java 9 as well.
In this post I’ll explain how you can run Java 9 workspaces in Eclipse Che.
Eclipse Che uses the Eclipse JDT (Java Development Tools) to do all the Java language services in the IDE (code completion, refactoring, etc...). Now that Eclipse Che is moving towards using only LSP (Language Server Protocol) implementations it’s easier to maintain these language services, and there is a clear separation between the
IDE part and the
With Che 5.x, we had a JDT instance running on the server side. …
Working on Eclipse Che and Red Hat Code Ready Workspaces Twitter: @florentbenoit