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 core libraries Kernel libraries used by all products. When there’s a change in Carbon core, we release a new Carbon version in a specific name. For 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 is called Turing. After releasing Carbon core, WSO2 releases the other ).
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 chunks. A chunk is a collection of products released togethera 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, Turing chunk 1 contains WSO2 DSS, WSO2 AS, and WSO2 IS. Building a chunk automatically downloads Carbon core libraries into your environment and builds all products that are released in the chunk on top of it.You can download WSO2 Turing chunk 1 source code anonymously of the Turing platform release contains Carbon 4.2.0 plus Data Services Server 3.1.0, Application Server 5.2.0, and Identity Server 4.5.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).
Data Services Server 3.1.0 is released in Turing chunk 1, which you can download using the checkout command as shown below
| Anchor | ||||
|---|---|---|---|---|
|
<local-platform-directory> with a meaningful name, such as wso2carbon-platform):...
Building the product
| Anchor | ||||
|---|---|---|---|---|
|
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-01 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-01/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. |
...