Currently, most Scala developers use Intellij IDEA as their main tool to write code. While it is a wholesome and tested solution, it might not suit everybody’s needs. A lot of people are using Eclipse as their editor of choice and the current solution, Scala IDE that is based on Eclipse, is no longer actively maintained. Metals is a Language Server Protocol (LSP) implementation enables users of Eclipse to enjoy rich IDE capabilities such as code completion, rename, diagnostics, goto definition and more.
An increasing number of tool providers are considering to offer their rich-client tools as a service in the Cloud, but not too many got already started. New technologies and platforms, such as the language server protocol (LSP), the Monaco Editor, Eclipse Theia, Eclipse Che, and Eclipse Graphical Language Server Platform (GLSP) are key enablers for achieving this goal. In this talk, we want to share our experiences made in an early Cloud migration project of a real industrial tool using those technologies.
With technologies like Quarkus and GraalVM emphasizing the importance of Java ecosystem in the cloud, good language support becomes important across various IDEs.
The JDT project has been around for a long time so it would be nice if all could benefit from the work that has gone into it, rather than having to reinvent the wheel.
While the Language Server Protocol (LSP) has quickly become an industry standard in the devtools domain and Eclipse IDE promptly got support for it with the Eclipse LSP4J and LSP4E projects, LSP is only targetting the code edition activity. However, code edition is just one activity amongst others for a developer, and some would argue that it's not the main use-case that justifies usage of an IDE over a simple text editor.
This talk shows how to use language servers to enhance the existing Java tooling in Eclipse. We explain how language servers can be integrated into JDT so that they work together in a seamless way using the LSP4E project and what custom code needs to be written for that integration.
Apache Camel is a well-known largely used integration framework which is providing different DSLs most notably inside Java and XML documents.
Dedicated tools are currently available only in 2 different IDEs, each with a very different set of features and no factorization between both. Most Apache Camel users don’t take into account existence of Camel Tooling in the choice of their IDE, as they focus on other criteria, so they miss to use the recommended tools. How to bring tooling to them?
Domain-specific languages (DSLs) are a powerful tool to capture arbitrary abstractions of an application domain and map it to code. Eclipse really shines when it comes to integrating DSLs in rich-client workbenches, but how about web-based IDEs?
In this talk you will learn how to bundle the power of four Eclipse frameworks to build a cloud-based IDE with support for your own DSLs:
The all-new Spring Tools 4 are a complete re-write of the popular Spring Tools for Eclipse. Based on the Language Server Protocol, they can be used in various environments, like Eclipse, Visual Studio Code, Atom, and more. This session takes a look behind the scenes of the new Spring tools, and while doing that, covers: