Petals Studio is an Eclipse _product_, made up of _plug-ins_ that are organized as _features_.
As a reminder, notice that the general Eclipse architecture was described [here to explain how to update the studio|Updating Petals Studio].

h1. Feature organization

Petals plug-ins are part of 3 of the 4 features.
In fact, plug-in dependencies cross feature boundaries.

{gliffy:name=Studio_Plugins|align=center|alt=Petals Studio's main plug-ins|version=10}

\\
{note}Although the plug-in organization was represented as a tree, it is in fact more like a graph.
As an example, some component plug-ins also use directly common plug-ins (\*.petals.common.\*).{note}

{note}The plug-in that defines the product (Petals Studio's plug-in) does not appear on this diagram.
It is independent and defines the welcome page and splash screen. It also contains the *.product file.{note}

h1. Build

h2. PDE Build

Petals Studio can be exported manually with the Plugin Development Environment (PDE).
Select *File > Export* and then *Plug-in Development > Eclipse product*.
Select _com.ebmwebsourcing.petals.studio/petals-studio.product_ in the configuration list and complete the properties before starting the build.

!petals-studio-dev-export.jpg!

\\
{tip}Notice that to build the studio for several platforms, the _Eclipse Delta Pack_ is required.{tip}

h2. Maven Build

The studio can now be built with Maven 3 and Tycho.
To build the studio with Maven, check the entire trunk (or desired tag), open a command line at the root and execute *mvn clean install*.
It will build a studio for several platforms.

\\
{note}Tycho only works with Maven 3.
Tycho is a Maven plugin that allows to build Eclipse plug-ins. These projects are not typical Maven projects.{note}