Building from Source

WSO2 invites you to contribute by downloading the source code from the GitHub source control system, building the product and making changes, and then committing your changes back to the source repository. The following sections describe this process:

Building from source is optional. Users who do not want to make changes to the source code can simply download the binary distribution of the product and install it.

Downloading the source

WSO2 products are built on top of WSO2 Carbon Kernel, which contains the Kernel libraries used by all products. When there are changes in the Carbon Kernel, they are bundled and released in a new WSO2 Carbon version (for example, WSO2 Carbon 4.3.0). You can download the complete WSO2 Kernel release using the following repository: https://github.com/wso2/carbon4-kernel, which is recommended if you intend to modify the source.

After downloading the source of the Carbon Kernel, execute the following commands to download the source of the product:

Clone carbon-device-mgt. The folder will be referred to as <CARBON_DEVICE_MGT> throughout the documentation.
```
git clone https://github.com/wso2/carbon-device-mgt.git
```
Clone carbon-device-mgt-plugin. The folder will be referred to as <CARBON_DEVICE_MGT_PLUGIN> throughout the documentation.
```
git clone https://github.com/wso2/carbon-device-mgt-plugins.git
```
Clone product-mdm. The folder will be referred to as <PRODUCT_MDM> throughout the documentation.
```
git clone https://github.com/wso2/product-mdm.git
```

After the source code is downloaded, you can start editing. However, it is recommended to run a build prior to changing the source code to ensure that the download is complete.

Editing the source code

Now that you have downloaded the source code for the Carbon project from GitHub, you can prepare your development environment and do the required changes to the code.

To edit the source code in your IDE, set up your development environment by running one of the following commands:

IDE	Command	Additional information
Eclipse	`mvn eclipse:eclipse`	http://maven.apache.org/plugins/maven-eclipse-plugin
IntelliJ IDEA	`mvn idea:idea`	http://maven.apache.org/plugins/maven-idea-plugin

If you are using a later Eclipse version and if you get errors (library path etc.) when trying to import the source code using the Existing Projects into Workspace option, you can solve them by importing the source code as a Maven project. To do this; open Eclipse and click Import in the File menu and then click Existing Maven Projects as shown below:

Add the required changes to the source code.

Building the product

Ensure that the following prerequisites are in place before you build:

Make sure the build server has an active Internet connection to download dependencies while building.
Install Maven and JDK. For compatible versions, see Installation Prerequisites.
Set the environment variable MAVEN_OPTS="-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m" to avoid the Maven OutOfMemoryError.

Use the following Maven commands to build your product:

Command	Description
`mvn clean install`	The binary and source distributions.
`mvn clean install -Dmaven.test.skip=true`	The binary and source distributions, without running any of the unit tests.
`mvn clean install -Dmaven.test.skip=true -o`	The binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you have already built the source at least once.

In EMM, you need to build the three repositories mentioned under downloading the source in the given order. Once the build is complete you will find the pack in the <EMM_SOURCE_HOME>/modules/distribution/target directory, as wso2emm-2.0.1.zip.

By default the pack you build includes the Android operations. To include the iOS operations you need to configure the pack with the iOS client configurations and iOS server configurations.

Committing your changes

You can contribute to WSO2 products by committing your changes to GitHub. Whether you are a committer or a non-committer, you can contribute with your code as explained in the Get Involved section.