Page Comparison

...

...

...

...

...

...

...

...

WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system, building the product and  and making changes, and then then committing your changes back  back to the source repository. (For more information on Subversion, see see http://svnbook.red-bean.com.) The following sections describe this process:

...

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 new WSO2 Carbon version  version (for example, WSO2 Carbon 4.2.0).

A WSO2 platform release is a set of WSO2 products based on the same Carbon release. For example, Turing is the platform release name for WSO2 Carbon 4.2.0 and the WSO2 products that are based on it. Usually, not all products in a platform get released at the same time, so they are released in in chunks, each of which contains the Carbon release and a subset of products. For  For example, chunk 6 8 of the Turing platform release contains the Turing platform release contains Carbon 4.2.0 plus API Manager plus Task Server 1.61.0, Identity Data Services Server 43.62.0 , and Storage Server 1and Complex Event Processor 3.1.0. When you want to build a product from source, you download and build the appropriate platform chunk. (To determine which chunk to use for a specific product version, see the Release Matrix).API Manager 1.6.0 is released in Turing chunk 6, which you can download using the checkout command as shown below Anchordirectorydirectory(replace <local-platform-directory> with a meaningful name, such as wso2carbon-platform)0 . 

Checking out the patches

Before checking out the product source, you need to checkout the patches related to the Carbon chunk using the following command.

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0 <local-platform-directory-1>

Downloading the product source

For products based on WSO2 Carbon 4.2.0, use the below command to download the product source:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-<release-chunk06chunk>/ <local-platform-directory-2>

Replace <release-chunk> with the release chunk, on which the specific product version is based on. To find out the respective release chunk, see the Release Matrix. For example, for products based on Chunk 08 of WSO2 Carbon 4.2.0, the command is as follows:

$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform-directory>
/tags/turing-chunk08/ <local-platform-directory-2>

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 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, follow the steps below to solve them by importing the source code as a Maven project.

1. Build the source using the command: mvn clean install
2. Open Eclipse and click Import in the File menu and then click Existing Maven Projects as shown below: 
   Image Added

Building the product 

Anchor
build build

Before you buildFollow the instructions below to build the product after editing the source code:

1. Install Maven and JDK. See See  Installation Prerequisites for  for compatible versions. 
2. Set the environment variable variable  MAVEN_OPTS="-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m"to  to avoid the Maven Maven OutOfMemoryError.

...

1. Navigate to each folder representing the patches within the  <local-platform-

...

1. directory-1> and run the following Apache Maven commands to build the patches. For information on the patches, which are applicable for the respective Carbon chunk release, go to Release Matrix. 

   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:

...

1. For products based on Carbon 4.2.0, to create complete release artifacts of the products released with this chunk version, including the binary and source distributions, go to     <local-platform-directory-2>/ product-releases/ <release-chunk>/   directory and run the Apache Maven commands stated in the above step.  To build only a selected product/s , open   <local-platform-directory-2>/product-releases/<release-chunk>/products/pom.xml  file, and comment out the products you do not want to build and run the relevant Maven command.

Committing your changes  

Anchor
commit commit

If you are a committer, you can commit your changes using the following command (SVN will prompt you for your password):

...