OpenCms Days 2013 - Gradle based OpenCms build automated setup

966 views
821 views

Published on

The build process for OpenCms 9 is using Gradle ( www.gradle.org ) instead of Apache Ant. The great advantage of the Gradle build process is an integrated dependency management so that libraries required to build OpenCms are downloaded automatically.

Moreover, OpenCms 9 provides a script based setup in addition to the traditional web interface. This allows the installation of OpenCms directly from the command line.

In this 2 part workshop, Tobias will first demonstrate how the new Gradle based build process in OpenCms 9 works. He will explain how to configure popular IDEs such as Eclipse to build the OpenCms core as well as individual module extensions. Tobias will then present the automatic setup process and show how to configure various options for the OpenCms installation.

Published in: Technology, Sports
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
966
On SlideShare
0
From Embeds
0
Number of Embeds
172
Actions
Shares
0
Downloads
29
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

OpenCms Days 2013 - Gradle based OpenCms build automated setup

  1. 1. Tobias Herrmann, Alkacon Software Workshop Gradle and automated setup with OpenCms 02.10.13
  2. 2. ●Why use Gradle over Ant? ●The OpenCms build script ●Setup your own OpenCms Gradle project ●Automated setup ●Continuous integration – automated everything 2 Agenda
  3. 3. ●Gradle build scripts: ●Sensible conventions ●Highly flexible ●Easy to read ●Easier to maintain ●Can do more with less ●Dependency management 3 Why Gradle?
  4. 4. ●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
  5. 5. ●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
  6. 6. ●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
  7. 7. ●Project layout: 7 Build your own
  8. 8. ●Gradle build file 8 Build your own
  9. 9. ●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
  10. 10. ●Setup properties 10 Automated setup
  11. 11. ●Automated builds ●Automated testing ●Automated code analysis ●Automated deployments ●Find bugs early 11 Continuous integration
  12. 12. ●Any Questions? 12 Any Questions? Fragen? Questions ? Questiones? ¿Preguntas?質問
  13. 13. Tobias Herrmann Alkacon Software GmbH http://www.alkacon.com http://www.opencms.org Thank you very much for your attention! 13

×