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:
...
| Info |
|---|
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. |
...
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 chunks, each of which contains the Carbon release and a subset of products. For example, chunk 8 5 of the Turing platform release contains Carbon 4.2.0 plus Task Server 1plus Application Server 5.2.1, Business Process Server 3.1.0, and Data Services Server 3.2.0 and Complex Event Processor 31.1.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 httpscheckout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0 <local/ <local-platform-directory-1>
| Info |
|---|
Replace |
...
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 05 of WSO2 Carbon 4.2.0, the command is as follows:
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk08chunk05/ <local-platform-directory-2>
...
- 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. Navigate to each folder representing the patches within the
<local-platform-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 installThe binary and source distributions of the chunk release.
mvn clean install -Dmaven.test.skip=trueThe binary and source distributions, without running any of the unit tests. mvn clean install -Dmaven.test.skip=true -oThe 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. - 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.xmlfile, and comment out the products you do not want to build and run the relevant Maven command.
| Info |
|---|
After building the source, you can find the artifacts/product binary distribution package of the product in the |
Committing your changes
| Anchor | ||||
|---|---|---|---|---|
|
...