loading table of contents...

Chapter 4. Quick Start

This chapter presents the basic steps to set up a CoreMedia Studio development environment quickly.

Setting Up the Workspace

CoreMedia Digital Experience Platform 8 comes with a fully preconfigured, Maven-based development workspace. Details on how to get and set up your development environment are described in the [CoreMedia Digital Experience Platform 8 Developer Manual] You will find guidance for the following topics:

  1. Required third-party software, such as Maven.

  2. Getting CoreMedia Project.

  3. Installing CoreMedia Project.

  4. Configuring all components.

  5. Building the workspace.

  6. Starting the components.

The recommended development setup is to use the studio module in the workspace, which is placed under modules/studio.

Setting Up the IDE

Once you have set up the workspace, you may configure your IDE as described in Section 6.3, “IDE Support”. If you are using IntelliJ IDEA, this means that you need to get the plugin Jangaroo 0.9, which you can install via IDEA's plugin manager. There are other Jangaroo plugins available in that dialog ("Jangaroo Language", "Jangaroo EXML", and "Jangaroo"), which are intended for older releases and must not be activated together with the current plugin Jangaroo 0.9.

Building

A detailed description on how to build the CoreMedia Studio module can be found in Chapter 6, Using the Development Environment. If you are using IntelliJ IDEA and the IDE is set up correctly, you can build the whole project via Maven from within the IDE. If you prefer building from the command line, you can do it by using standard Maven commands like 

mvn clean install -DskipTests

The CoreMedia Studio application can then be launched by changing into the modules/studio/studio-webapp directory and using the following command: 

mvn tomcat7:run

More details on how to build and start CoreMedia Studio, as well as how to run tests with it, are described in Section 6.2, “Build Process”.

Debugging

Firebug is the recommended JavaScript debugger. To facilitate debugging, single class JavaScript files of the CoreMedia Studio components can be loaded by attaching 

#joo.debug

to the CoreMedia Studio URL. An Ext JS debugger allowing component inspection can be invoked by executing the following JavaScript statement: 

Ext.log('')

Refer to Section 6.4, “Debugging” for more details on how to debug.

If you have finished these steps you are ready to customize CoreMedia Studio as described in Chapter 7, Customizing CoreMedia Studio.

Prev   Next
 Home