The popularity of the Kubernetes platform is continuously increasing... for good reasons! It's a wonderful modular platform made out of fundamentals orthogonal bricks used to defined even more useful bricks. It enables a DevOps friendly envrionnment where microservices and continously delivery feel at home.
If you have not yet dig into what is usually defined as a Cluster Operating System, it's time to catch-up! This thorough introduction to Kubernetes will cover:
As part of the Eclipse Common Build Infrastructure (CBI) initiative the Eclipse Foundation provides a build environment for projects to build, test, deploy and deliver Eclipse related software. Come and learn how it works and what's cooking!
It started with a single Hudson build server (Shared instance) for multiple projects. In 2013 the “Hudson instance per project” (HIPP) concept was introduced that allowed every Eclipse project to have a dedicated CI server. Since Hudson was not longer maintained, about 200 CI instances were converted to Jenkins in early 2018.
Many business applications are data-driven and require viewing and entering data in forms… countless forms. Unfortunately, writing HTML5-based web forms manually is still error-prone and tedious, even with the help of modern web application frameworks like Angular. A form may seem simple at first, but you usually need to add live validation and error markers, rule-based visibility, input restrictions, and the like. As you can imagine, it quickly gets out of hand. Finally, when you have many of these forms the code becomes unmaintainable.
Slowly but steadily, selected developer tools are being migrated to web technology using emerging technologies such as Atom, Eclipse Che, Monaco, Theia, or LSP. Those technologies are mainly dealing with textual editing (source code, DSLs), but what about non-textual modeling? Many existing tools are essentially modeling tools. They allow you to create models that can be manipulated in tree- and form-based editors as well as in graphical editors.
Eclipse Theia is a modular framework for building cloud and desktop IDEs. It is implemented in TypeScript and leverages state of the art technology as the Monaco editor and the language server protocol (LSP) which also powering VS Code. Theia has been designed in open-source by TypeFox and Ericsson through 2017.
The LSP is a protocol between editors or IDEs and language servers providing language features like diagnostics, auto-completion, find references etc. Over last year it has got wide adoption among different tools and languages including Theia and Xtext.
The Target Communication Framework (TCF) is an already established mechanism for tasks like target interaction, file operations and inferior control. Using this framework, the TCF debugger was built, providing an easy-to-retarget debugger framework powered by a target-agnostic debug engine. The dominant use-case of the upstream debugger agent has been the debugging of software threads with the help of the OS infrastructure (sofware-only debugging).
Eclipse plugin on diet: Road to thin client application
After releasing the first version of our code improvement Eclipse plugin, we got feedback of people wanting to put our product into development pipelines. Multiple prototyping rounds lead us to develop a Maven plugin, which embedded the business logic part of our plugin. This way code improvements could be executed and parametrized the Maven plugin way. Our next step is cloud integration and running our plugin as a microservice.
For the past several years, we have been discussing about the next generation IDE for Eclipse, about how tools we have in Eclipse could be running on both desktop and cloud. We are seing new standards such as "Language Server Protocol" and "Debug Adapter Protocol" and new platforms to build tools for the cloud. During this session, we'll present how Eclipse Che and Theia can be used to move tools to the cloud and leverage the new technology standards.
The journey of building developer tooling has never been as exciting as it is right now. Eclipse Che is getting more and more mature, bringing collaboration and teams capabilities for developer workspaces. Theia, integrated in Eclipse Che, is providing the foundations for a modern and extensible web IDE. With the rise of cloud development platforms, we see the industry defining new server protocols, such as "Language Server Protocol" and "Debug Server Protocol" which allow to bring tooling on a wide range of platforms, such as Eclipse, Eclipse Che and VS Code.
Jakarta EE is the new name for the evolution of JavaEE within the Eclipse Foundation. Many people think of Java EE as a heavyweight Enterprise solution for big scale. In this talk I would like to dispel this myth demonstrating how light-weight JavaEE based microservices can run on small platforms and integrate with IOT technologies like Eclipse Mosquito for messaging. In this code driven talk you will learn how to use the JavaEE JCA specification to create a connector to MQTT and to drive event driven microservices running on JavaEE on Raspberry PIs.
Have you ever needed to compare and merge heterogeneous domain-specific models (with both textual and graphical syntaxes)? Or maybe you needed to review changes on graphical models? We did.
World around Java is changing at a fast pace. Java will have twice-yearly releases starting March 2018. At the time of this writing, Java 10 is expected to be out in March 2018 and Java 11 in September 2018. Not far away in September 2017 we had the Java 9 release.
I will demonstrate some new concepts added in Eclipse JDT to support Java 9. Java 9 introduced Java modules and I will show how a user can create a Java module, set up it's modulepath and classpath, can patch, limit or add exports in the Java module.
I will also demonstrate other new features added for Java 9 -
Lifting and shifting existing applications to the Cloud is a common task for many deveopers these days. This session will explain 3 common scenarios for moving Java EE standards based applications to Azure using concepts applicable to other cloud environments as well. One is of course using Containers and Kubernetes; Second is by using a platform runtime such as Azure AppService. And the third is by using Service Fabric. In the end, we will see the differences, pros/cons, and also open for Q&A.
Eclipse JDT (Java Development Tools) provides a lot of powerful features and capabilities, and it has been reloaded with more exciting features for the upcoming Eclipse Photon (4.8) release. In this session, I will showcase some of the cool new features which have been added in JDT to make your experience more convenient and pleasant.
Java 9 is here with Jigsaw modularity and Java 10 introduces the context-sensitive keyword 'var'. I will demo some of the new tooling features provided by JDT as part of its support for the new Java releases like:
Most data has a location component that, once enabled, opens previously unseen avenues of analysis and understanding. This is especially relevant for Big Data analysis purposes.
Looking at data from a geographical perspective provides new insights and explanations often unrecognized without a spatial eye, but vital to understanding and managing activities and resources: to see the unseen!
On March 2018, Microsoft released the source code of one of its core Azure services: Service Fabric is now open sourced on GitHub - https://github.com/Microsoft/service-fabric/. This talk will introduce Java developers to the platform: how to download and install Service Fabric on Linux, and how to run an application designed for it.
With Xtext it is really easy to build smart editors and IDE integration for your textual languages. And “smart” just turned into “brilliant”.
The latest Xtext release ships with a new infrastructure (called ChangeSerializer) for semantic editing, which allows to implement significantly more powerful Refactorings and QuickFixes for your language. In this talk I will:
Eclipse Platform 4.8 introduced support for parallel builds in the workspace. This feature is placed at the lowest level of the workspace so it can easily be profitable to any adopter without specific adoption effort, besides respecting usual good practices. This can in theory turn the Eclipse workspace into one of the fastest polyglot build engines in developer world.
In this presentation, we’ll explain what is the value to expect from this parallel builds (mostly performance gain and faster availability of project output).
In this 5min presentation, we’ll show how the best-of-breed approach can now efficiently be leveraged in Eclipse IDE to quickly provide a good language support by consuming existing pieces of technologies such as language servers, TextMate grammars and Command-Line interfaces.
We’ll use the examples of Eclipse aCute (for C#) and Eclipse Corrosion (for Rust) as case-studies.