Apache Camel URI completion in Eclipse XML Editor

Apache Camel empowers you to define routing and mediation rules in a variety of domain-specific languages, including a Java-based Fluent APISpring 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 HTTPActiveMQJMSJBI, 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”


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

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”


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

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”