IDE

Eclipse Che 6.6 Release Notes

Eclipse Che 6.6 Release Notes

dneary
By Dave Neary

[This article is cross-posted from the Eclipse Che Blog.]

Eclipse Che 6.6 Release Notes

Eclipse Che 6.6 is here! Since the release of Che 6.0, the community has added a number of new capabilities:

  • Kubernetes support: Run Che on Kubernetes and deploy it using Helm.
  • Hot server updates: Upgrade Che with zero downtime.
  • C/C++ support: ClangD Language Server was added.
  • Camel LS support: Apache Camel Language Server Protocol (LSP) support was added.
  • <strong”>Eclipse Java Development Tools (JDT) Language Server (LS): Extended LS capabilities were added for Eclipse Che.
  • Faster workspace loading: Images are pulled in parallel with the new UI.

Quick Start

Che is a cloud IDE and containerized workspace server. You can get started with Che by using the following links:

Continue reading “Eclipse Che 6.6 Release Notes”

Share
Apache Camel URI completion: easy installation for Eclipse, VS Code, and OpenShift.io

Apache Camel URI completion: easy installation for Eclipse, VS Code, and OpenShift.io

apupier
By Aurélien Pupier

Discoverability and ease of installation of Apache Camel tooling based on the Language Server Protocol has been improved. Manual download and installation of binaries is no longer necessary!  For the Eclipse desktop IDE and the VS Code environment you can now find and install the Camel tooling directly from the marketplaces for each development environment.

Camel Language Server is now also available in Red Hat OpenShift.io!

In this article, I will show you how you can install Camel tooling via the marketplaces for Eclipse and VS Code.  I will also show how to enable Camel tooling in your OpenShift.io workspace.

Continue reading “Apache Camel URI completion: easy installation for Eclipse, VS Code, and OpenShift.io”

Share
Eclipse Che’s Plans for 2018

Eclipse Che’s Plans for 2018

slemeur
By Stevan LeMeur

 

2018 has been a busy year already, and we’re not even halfway through.  Eclipse Che 6 brought team and enterprise features including multi-user and multi-tenancy as well as a large number of other great capabilities (you can read all about it in our Che 6 release post).

We followed Che 6 GA with already 4 minor releases and the community worked hard in order to add even more capabilities:

  • Helm chart for Kubernetes deployment
  • C/C++ intellisense with integration of ClangD
  • Recover capabilities for OpenShift/Kubernetes
  • And almost 150 bug fixes

Continue reading “Eclipse Che’s Plans for 2018”

Share
Apache Camel URI completion in Eclipse XML Editor

Apache Camel URI completion in Eclipse XML Editor

apupier
By Aurélien Pupier

Apache Camel empowers you to define routing and mediation rules in a variety of domain-specific languages, including a Java-based Fluent API, Spring or Blueprint XML Configuration files, and a Scala DSL. Apache Camel uses URIs to work directly with any kind of Transport or messaging model such as HTTP, ActiveMQ, JMS, JBI, SCA, MINA or CXF, as well as pluggable Components and Data Format options. Apache Camel is a small library with minimal dependencies for easy embedding in any Java application.

Continue reading “Apache Camel URI completion in Eclipse XML Editor”

Share

Deliver support for new languages in Eclipse IDE faster with Generic Editor and Language Servers

mistria
By Mickael Istria

If you’re a regular on this blog, you’re probably well aware of Red Hat’s efforts in improving the Eclipse IDE and of the rise of Language Servers Protocol to develop common developer tools. Red Hat fully jumped on this opportunity to better factorize and share language-specific logic which is very likely to benefit to multiple editors, IDEs and languages at once. It also better separates the concerns of what an editor or IDE is supposed to do (text edition, integration with SCM, debug and deployment workflows…) with the target language itself. With this approach, a single language server can enable language features to multiple development tools at once, and a single development tool can be made more generic to support new languages for free, just by binding to the language server through the protocol.

Continue reading “Deliver support for new languages in Eclipse IDE faster with Generic Editor and Language Servers”

Share
Red Hat and Eclipse IDE, looking back at Neon and forward at Oxygen

Red Hat and Eclipse IDE, looking back at Neon and forward at Oxygen

mistria
By Mickael Istria

Last June, Eclipse IDE had a great release, named Neon. It features, among many other less visible but still quite useful improvements, many new functionalities for everyone. If you did not migrate yet and are still using an older Eclipse version, just move to Neon right now, it’s worth it!

For this Neon release, Red Hat managed to increase its contributions to the Eclipse IDE. The 2 main teams doing Eclipse IDE development (to package Eclipse IDE as .rpm for Fedora Linux and Red Hat Enterprise Linux, and to develop JBoss Tools Eclipse plugins and Red Hat JBoss Developer Studio) could spend more time working upstream, directly on the Eclipse IDE and related projects.

If you follow some Eclipse mailing-lists or Bugzilla discussions, you’ll see that Red Hat developers are involved in many areas about improving the Eclipse IDE: look and feel, usability, necessary feature set, Linux, new trends… The intention of Red Hat regarding Eclipse IDE is clear and public: we all want the Eclipse IDE to remain great and even greater than it has even been and probably the greatest desktop IDE on the market – and this continuously. Together with the numerous other motivated contributors to the Eclipse community and ecosystem, we’re confident that’s something achievable.

Continue reading “Red Hat and Eclipse IDE, looking back at Neon and forward at Oxygen”

Share