WSO2 invites you to contribute by by checking out the source from 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:
...
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 10 1 of the Turing platform release contains Carbon 4.2.0 plus DSS 3.1.0 and IS 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).
You need to checkout the patches related to the Carbon chunk using the following command, before checking out the product source. Replace <local-platform-directory-1> and with a meaningful name, such as wso2carbon-platform.
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/ <local-platform-directory-1>
WSO2 MB 2.2.0 is released in Turing chunk 1011, which you can download using download using the checkout command command as shown below (replace replace <local-platform-directory> with with a meaningful name, such as wso2carbon-platform) :
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk10chunk11 <local-platform-directory>
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 See Installation Prerequisites for for compatible versions.
- Set the environment variable variable
MAVEN_OPTS=”"-Xms1024m -Xmx4096m -XX:MaxPermSize=1024m”"to avoid the Maven MavenOutOfMemoryError.
To create complete release artifacts of the products released with this chunk version, including the binary and source distributions, go to to <local-platform-directory> /repos/wso2/carbon/platform/tags/turing-chunk10chunk11/product-releases/chunk-10 11 and run the following following Apache Maven commands commands. To build only a selected product/s, open the the <local-platform-directory>/repos/wso2/carbon/platform/tags/turing-chunk10chunk11/product-releases/chunk-1011/products/pom.xml file, comment out the products you do not want to build and run the relevant Maven command.
| Command | Description |
|---|---|
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. |
...
| IDE | 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 changeschanges
| Anchor | ||||
|---|---|---|---|---|
|
If you are a committer, you can commit your changes using the following command (SVN will prompt you for your password):
...