Tobias Herrmann, Alkacon Software

Workshop

Gradle and automated setup with OpenCms

02.10.13

●Why use Gradle over Ant?●The OpenCms build script●Setup your own OpenCms Gradle project

●Automated setup

●Continuous integration – automated everything

2

Agenda

●Gradle build scripts:●Sensible conventions●Highly flexible●Easy to read●Easier to maintain●Can do more with less

●Dependency management

3

Why Gradle?

●What is happening during the OpenCms build?●The opencms.jar●Module jar files●GWT resources●Module zip files●The WAR file●The upgrade wizard●The distribution

4

The OpenCms build

●Important tasks:●bindist – the OpenCms distribution●updater – the upgrade wizard●war – the OpenCms WAR●jar – the opencms.jar file●dist_{module name} – a single module●test – runs the OpenCms test cases●clean – cleans the build directory

5

The OpenCms build

●Build properties – gradle.properties●build_directory – choose your build directory●external_directories – external module directory●max_heap_size – Xmx setting for build process

6

The OpenCms build

●Project layout:7

Build your own

●Gradle build file8

Build your own

●Why use an automated setup?●How is it done?●Unpack the WAR file●Run /WEB-INF/setup.sh or /WEB-INF/setup.bat●Provide the setup properties

– org/opencms/setup/setup.properties.example

9

Automated setup

●Setup properties10

Automated setup

●Automated builds●Automated testing●Automated code analysis●Automated deployments

●Find bugs early

11

Continuous integration

●Any Questions?

12

Any Questions?

Fragen?Questions ?

Questiones?¿Preguntas?質問

Tobias Herrmann

Alkacon Software GmbH

http://www.alkacon.com

http://www.opencms.org

Thank you very much for your attention!

13