WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system, building the product and making changes, and then committing your changes back to the source repository. (For more information on Subversion, see http://svnbook.red-bean.com.) 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.
Checking out 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.2.0 release). A platform is released on top of a WSO2 Carbon release.
A WSO2 platform release is a bunch of WSO2 products based on the same Carbon release. For example, Turing is the platform release name for WSO2 Carbon 4.2.0. Therefore, a given platform release is based on the same Carbon Kernel. Usually, not all products in a platform get released at the same time. They are released in chunks. A chunk is a subset of products in a platform that is released together. For example, Turing chunk-02 contains WSO2 APIM 1.5.0 , WSO2 ELB 2.1.0 , and WSO2 G-Reg 4.6.0. When you want to build a product from source, you can download and build this chunk release. It automatically downloads WSO2 Carbon Kernel libraries into your environment and builds all the products that are released in the chunk on top of it.
For more information on WSO2 releases, see the Release Matrix in our company website.
WSO2 APIM 1.5.0 is released in Turing chunk 2, which also contains . You can download WSO2 Turing chunk 2 source code anonymously using the checkout command as shown below (replace <local-platform-directory> with a meaningful name, such as wso2carbon-platform):
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk02 <local-platform-directory>
Building the product
Before you build:
- Make sure the build server has an active Internet connection to download dependencies while building.
- Install Maven and JDK. See Installation Prerequisites for compatible versions.
- Set the environment variable
MAVEN_OPTS=”-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m” to avoid the MavenOutOfMemoryError.
To create complete release artifacts of the products released with this chunk version, including the binary and source distributions, go to <local-platform-directory>/repos/wso2/carbon/platform/tags/turing-chunk02/product-releases/chunk-02 and run the following Apache Maven commands. To build only a selected product/s, open <local-platform-directory>/repos/wso2/carbon/platform/tags/turing-chunk02/product-releases/chunk-02/products/pom.xml file, comment out the products you do not want to build and run the relevant maven command.
| This command... | Creates... |
|---|---|
mvn clean install | The binary and source distributions of the chunk release. |
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've already built the source at least once. |
Setting up your development environment
Before you edit the source code in your IDE, set up your development environment by running one of the following commands:
| If you are using this IDE... | Run this 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 |
Committing your changes
If you are a committer, you can commit your changes using the following command (SVN will prompt you for your password):
$ svn commit --username your-username -m "A message"