In a previous article, I mentioned the growing set of supported IDEs/editors for the Apache Camel language. I’m happy to announce that this set has grown again. It is now possible to use CodeMirror with Apache Camel. CodeMirror is a lightweight, embeddable editor for web browsers.
Continue reading “Apache Camel Language support in CodeMirror”
A growing set of editors and IDEs provides specific tooling for development of applications based on Apache Camel. Historically, there was only Eclipse Fuse Tooling, which was based on the Eclipse Desktop IDE. Then, an IntelliJ plugin was created. Both of these tools are tightly coupled to the specific IDE APIs. Consequently, they have the drawback of not easily sharing the development effort.
Thanks to Language Server Protocol, with a core server and several configurations or small client development, Apache Camel Language can now be enjoyed on a growing set of environments:
Continue reading “A look at development environments with specific tooling for Apache Camel Language”
For my first and ongoing project as an intern at Red Hat, I’ve been working alongside Angelo Zerr and Fred Bricon to develop an implementation of the Language Server Protocol (LSP) for XML. Through the XML language server, developer tools like VSCode and Eclipse receive XML syntax highlighting and checking, code completion, document folding, etc. At the moment we appear to have the most feature rich XML language server implementation, including our Schema-based support which is an essential XML feature that we are most proud of. Combined, all these features make it much easier for developers to work on any type of project involving XML, from the comfort of their favorite editor or IDE.
Continue reading “XML Language Server and the VSCode Extension”
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”
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. It also 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 VS Code XML Editor and Eclipse Che”
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”
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”
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”
Java language server is an implementation of the language server protocol for Java. If you recall, language server protocol provides a common way for editors and IDEs to integrate with language smartness providers. By design, all of the language tooling magic happens on the Java language server, and can provide same level of smartness to tools that support the protocol. In fact, we are working with communities such as Eclipse Che to make this server available for their tools.
Continue reading Java Language Support for Visual Studio Code has landed
As you may recall, Red Hat recently announced support for a common language server protocol. Furthermore, we demoed our initial implementation for a Java language server during the DevNation keynote. I posted an earlier blog covering these topics, and I would like to do an update in this post on the progress we’ve made since DevNation.
Continue reading A week of hacking the Java Language Server
