In this session, we will specifically look at the tooling available as part of the development kit that assist in understanding the composition of our legacy application as well as help us work with the semantics of modularity feature. The aim of this session is to help audience to be able to use the in-built tooling effectively towards Java 11 migration.
Recent vulnerabilities in open source libraries, like Log4Shell [1], enforce every developer to stay up to date and to migrate existing software to the latest version available. It sounds easier than it is in reality. The path of migration isn't always straight forward, especially if a large software suite needs to be maintained. Personally, I'm getting a bit nervous when being confronted with the term "migration".
Are your applications still running on Java 8 or even older, unsupported versions? Or maybe you've already made the move to Java 11? Thinking about switching your application to run on Java 17 and not sure where to start? There is a lot to think about when it comes to planning a Java migration, but there are tools and strategies that can help!
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.
Are your applications running on Java 8? Thinking about switching your application to run on Java 11 or Java 12 and wondering about where to start? Come to this session to learn about the most significant changes that went into Java 11 and 12 that will impact your application migration. Topics will include the removal of APIs (such as Java EE packages) and behavior changes resulting from moving an application from running on Java 8 to running on Java 11 and 12.
Akuiteo is a french company that publishes Akuiteo ERP, a software management platform for services companies.
Our main front-end product is an Eclipse RCP-based application. This product was launched in 2007, and our last technical migration (from RCP 3.5 to RCP 3.7) occured in 2012.
After 5 years, it was time to enter in a new era by changing the engine and migrating to e4 !
I'll present the different steps, the doubts, the pitfalls and eventually the success !
The goal of MicroProfile.IO is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space.
However, some of the microprofile implementations are completely different 'servers', like the KumuluzEE server. So how can you migrate easily from your favorite Java EE server to a MicroProfile implementation?
A Java release every 6 months? Awesome! But maybe you’re worried about upgrading and deprecation? Don’t be! This session highlights the tools and concrete strategies necessary for adapting to the new OpenJDK release cycle. Come learn from JVM developers how to prepare for continuous change without losing your mind.
QIVICON is an Eclipse SmartHome based solution from Deutsche Telekom AG. It utilises OSGi to provide a modular Java runtime.
Since the beginning, QIVICON leveraged Eclipse PDE with Maven & Eclipse Tycho as its build technology but over the time, the complexity increased. It became hard to get an overview and manage the runtime and build dependencies. Especially maintaining target configurations for IDE and CI/CD build, having different embedded gateways for installation increased complexity significantly.
There is currently a big hype surrounding web-based tooling . New projects and frameworks are popping up and existing projects get more traction both in- and outside the Eclipse ecosystem, e.g. Eclipse Che, Eclipse Theia, Visual Studio Code, Atom, Eclipse Drigible, and Eclipse Orion. While the dissemination of web-based tools in the real world is still relatively low, almost every tool project will eventually deal with the question of how to migrate to a web-based platform.
