FROM NOTHING TO COMPLETE ENVIRONMENT WITH MAVEN, OOMPH & DOCKER. Max Bureck, 21. June 2017

Size: px

Start display at page:

Download "FROM NOTHING TO COMPLETE ENVIRONMENT WITH MAVEN, OOMPH & DOCKER. Max Bureck, 21. June 2017"

Charity Ray
6 years ago
Views:

1 WITH MAVEN, OOMPH & DOCKER Max Bureck, 21. June 2017

2 1. Disclaimer 2. Motivation 3. Demo 4. Recap, Conclusion, and Future Possibilities 2

3 3

4 FROM (ALMOST) NOTHING TO COMPLETE ENVIRONMENT Disclaimer: Prerequisites are Maven, Oomph & Docker Maven >= 3.0 Latest Eclipse installer Docker 4

5 Windows 10: Easiest Way to Make Docker Daemon Accessible From Eclipse 5

6 Motivation: Target Domain Introduction Writing a transformation service 6

7 Motivation: Target Domain Introduction Developing ModelBus services should be simple Usually first task for new team member: Read ModelBus user guide Create example ModelBus services 7

8 Motivation: Setup Experience, Step 1 Setup Action: Install ModelBus server Configure ModelBus server Problems: User forgets to set mandatory environment variable User forgets to add SVN plugins (for legal reasons not part of ModelBus distro) 8

9 Motivation: Setup Experience, Step 2 Setup Actions: Install Eclipse Install ModelBus TeamProvider plugins Configure TeamProvider and target platform Problem: User does not add plugins for standalone services to target platform 9

10 Motivation: Setup Experience, Step 3 Setup Action: Create projects for service interface, provider - and consumer service Problem: User forgets to add mandatory plugin dependency 10

11 Motivation: Setup Experience, Step 4 Setup Action: User creates launch configurations for provider and consumer projects Problem: User forgets to set one or more start-levels for plugins 11

12 Motivation: Setup Experience, Step 5 Setup Action: User creates product definition for services (for standalone executable) Problems: User forgets to set one or more start-levels for plugins (again) Forgotten plugins in product definition 12

13 <project xmlns=" xmlns:xsi=" xsi:schemalocation=" <modelversion>4.0.0</modelversion> <groupid>org.modelbus.demo.service</groupid> <artifactid>org.modelbus.demo.service.releng</artifactid> <version>1.0.0-snapshot</version> <packaging>pom</packaging> <name>org.modelbus.demo.service.releng</name> <description>modelbus Demo Service Release Engineering</description> <properties> <tycho-version>1.0.0</tycho-version> <project.encoding>utf-8</project.encoding> <project.build.sourceencoding>${project.encoding}</project.build.sourceencoding> <java.version>1.8</java.version> <project.source.version>${java.version}</project.source.version> <project.target.version>${java.version}</project.target.version> <organization.name>fraunhofer FOKUS</organization.name> <organization.url> <organization.cc.name>system Quality Engineering (SQC)</organization.cc.name> <organization.cc.url>  <maven.deploy.skip>true</maven.deploy.skip> <timestamp>${maven.build.timestamp}</timestamp> <maven.build.timestamp.format>yyyy-mm-dd-hhmm</maven.build.timestamp.format> </properties> <profiles> </profiles> <profile> <id>all-modules</id> <activation> <activebydefault>true</activebydefault> </activation> <modules>../../plugins/org.modelbus.demo.service </modules> </profile> <profile> <id>provider-only</id> <modules>../../plugins/org.modelbus.demo.service.consumer../../plugins/org.modelbus.demo.service.provider../../features/org.modelbus.demo.consumer.dependencies.feature../../features/org.modelbus.demo.service.consumer.feature../../p2/org.modelbus.demo.service.consumer.product../../features/org.modelbus.demo.service.provider.dependencies.feature../../features/org.modelbus.demo.service.provider.feature../../p2/org.modelbus.demo.service.provider.product../../plugins/org.modelbus.demo.service../../plugins/org.modelbus.demo.service.provider../../features/org.modelbus.demo.service.provider.dependencies.feature../../features/org.modelbus.demo.service.provider.feature../../p2/org.modelbus.demo.service.provider.product </modules> </profile> <profile> <id>consumer-only</id> </profile> <modules>../../plugins/org.modelbus.demo.service../../plugins/org.modelbus.demo.service.consumer../../features/org.modelbus.demo.consumer.dependencies.feature../../features/org.modelbus.demo.service.consumer.feature../../p2/org.modelbus.demo.service.consumer.product </modules> <repositories>  <repository> <id>neon</id> <layout>p2</layout> <url> </repository>  <repository> <id>emf</id> <layout>p2</layout> <url> </repository>  <repository> <id>modelbus</id> <layout>p2</layout> <url> </repository> </repositories> <build> </build> </project> <plugins>  <plugin> <groupid>org.eclipse.tycho</groupid> <artifactid>tycho-maven-plugin</artifactid> <version>${tycho-version}</version> <extensions>true</extensions> </plugins> </plugin>  <plugin> <groupid>org.apache.maven.plugins</groupid> <artifactid>maven-javadoc-plugin</artifactid> <version>2.7</version> </plugin>  <plugin> <groupid>org.eclipse.tycho</groupid> <artifactid>tycho-p2-repository-plugin</artifactid> <version>${tycho-version}</version> <configuration> <finalname>${project.artifactid}-${project.version}</finalname> </configuration> </plugin> <plugin> <groupid>org.eclipse.tycho</groupid> <artifactid>target-platform-configuration</artifactid> <version>${tycho-version}</version> <configuration> <environments> <environment> <os>linux</os> <ws>gtk</ws> <arch>x86</arch> </environment> <environment> <os>linux</os> <ws>gtk</ws> <arch>x86_64</arch> </environment> <environment> <os>macosx</os> <ws>cocoa</ws> <arch>x86_64</arch> </environment> <environment> <os>win32</os> <ws>win32</ws> <arch>x86</arch> </environment> <environment> <os>win32</os> <ws>win32</ws> <arch>x86_64</arch> </environment> </environments> <dependency-resolution> <optionaldependencies>ignore</optionaldependencies> </dependency-resolution> </configuration> </plugin> FROM NOTHING TO COMPLETE ENVIRONMENT Motivation: Setup Experience, Step 6 Bonus Action: Create Maven Tycho build scripts Problems: Bundle IDs / Feature IDs have to match POM artifactids 13

14 Motivation: Setup Experience Conclusion 14

15 Motivation: Improving Setup Experience Use automation to get rid of error prone manual tasks of Installation of ModelBus server Installation and configuration of Eclipse + plugins Creation of service interface, provider, and consumer plugins Creation of launch configs and product definition Creation of Maven Tycho build scripts 15

16 Demo 23

17 Recap, Part 1 We used Maven archetype to generate Projects (service interface, provider, consumer, features, products) Maven build scripts Oomph setup file Dockerfiles for ModelBus server, provider service, consumer service Launch configs for build, run, debug 24

18 Recap, Part 2 We used generated Oomph setup to Install Eclipse Install plugins into Eclipse Configure Eclipse + plugins Configure target platform 25

19 Conclusion If your platform is based on OSGi / Eclipse tech: Consider Maven archetypes Use Oomph for (reproducible) Eclipse setups Consider Docker if your Eclipse based platform integrates with network services 26

20 Going Even Further (When Possible) Install prerequisites via package managers (apt, chocolatey, homebrew, etc.) Single shell script call for setup, literally starting from nothing Starting eclipse installer with Oomph setup file from command line Generating CI configuration (Jenkinsfile,.travis.yml,.gitlab-ci.yml, etc.) 27

21 Please Vote and Leave Comments 28

22 Thanks! Questions? 29

23 CONTACT Fraunhofer FOKUS Kaiserin-Augusta-Allee Berlin, Germany Max Bureck Senior Researcher Tel. +49 (0)

Set up Maven plugins in Eclipse. Creating a new project

Set up Maven plugins in Eclipse. Creating a new project In this tutorial, we describe steps for setting up a Maven project that uses libsbolj in Eclipse. Another tutorial follows this one which explains how we use SBOL 2.0 to represent the function of a state-of-the-art