Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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:

...

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 WSO2 platform release is a bunch set of WSO2 products based on the same Carbon release. For example, Turing is 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. They , so they are released in chunks. A chunk is , each of which contains the Carbon release and a subset of products in a platform that is released together. For example, Turing chunk-02  contains WSO2 APIM, WSO2 ELB, and WSO2 G-Regchunk 2 of the Turing platform release contains Carbon 4.2.0 plus API Manager 1.5.0, Elastic Load Balancer 2.1.0, and Governance Registry 4.6.0. When you want to build a product from source, you can download and build this the appropriate platform chunk. 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(To determine which chunk to use for a specific product version, see the Release Matrix in our company website).WSO2 APIM

API Manager 1.5.0 is released in Turing chunk 2, which also contains WSO2 ELB 2.1.0 and WSO2 G-Reg 4.6.0. You can download WSO2 Turing chunk 2 source code anonymously you can download using the checkout command as shown below

Anchor
directory
directory
(replace <local-platform-directory> with a meaningful name, such as wso2carbon-platform):

...

Building the product 
Anchor
build
build

Before you build:

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

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.

...