Page Comparison

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, refer http://svnbook.red-bean.com/.) The following sections describe this process:

...

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

...

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

3. 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 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.

4. 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>/repos/wso2/carbon/platform/tags/<WSO2-Carbon-version>/products/ directory  and run the Apache Maven commands stated in the above step. To build only a selected product/s, open  <local-platform-directory-2>/repos/wso2/carbon/platform/tags/<WSO2-Carbon-version>/products/pom.xml file, and comment out the products you do not want to build and run the relevant Maven command.

...