Duration: 32:04

2,229 views

7

Did the target plaftorm editor of Plugin Development Environment (PDE) ever made you tear your hair out? Did you ever wanted to create a modular target platform in order to build your product against several version of Eclipse? Also did you ever tried to properly set up the version of your exported packages by following semantic versionning guidelines? Then you know that PDE does not handle this things very well. This talk will present to you two tools built on top of PDE.

The first one eases the creation and maintenance of target platform definitions. The second one handles the versionning of exported packages automatically, using the existing API baseline tooling of PDE.

The target platform DSL editor and generator is a mature project that aims at providing a clean tooling to create, maintain and compose target platform definitions (https://github.com/mbarbero/fr.obeo.releng.targetplatform). During this talk, you will learn how to create a target platform definition with ease thanks to clever content assist. You will also learn how to create a modular target platform to compile and test your product on different versions of Eclipse. You will also see a glimpse of the internals and how it uses the Xtext framework.

The package baseliner tool (https://github.com/cbrun/baseliner) is more recent project that enriches MANIFEST.MF's export packages with computed versions. It automatically updates exported packages versions based on the current API baseline. It reuses the baseline defined in the Eclipse preferences. We will explain why it is important to properly set the version of the exported packages and you will learn how to setup and use the tool for your own project. Again, you will see the internals at a glance, most notably the workspace builder which is used under the hood and also the calls to the Bnd framework for the computation of versions.