Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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/platform/tags/turing-chunk11 <local-platform-directory>

Access through a firewall

If you are behind a corporate firewall that is blocking HTTP access to the Subversion repository, you can try the developer connection to the trunk. For example:

$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon wso2carbon

Access through a proxy

The Subversion client can be configured to access through a proxy. Specify the proxy to use in the "servers" configuration file in: 

  • "~/.subversion" directory for Linux/Unix
  • "%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")

The comments in the file explain what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.

For example, edit the 'servers' file and add something similar to the following:

...

Building the product 
Anchor
build
build

Following are the Apache Maven commands you can run to create complete release artifacts of WSO2 Business Rules Server, including the binary and source distributions. If you only want to build Business Rules Server, use the -Dproduct=brs option as shown. If you want to build the entire Carbon core project, omit the -Dproduct=brs option.

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=”-Xms768m -Xmx3072m -XX:MaxPermSize=1200m to avoid the Maven OutOfMemoryError.
CommandDescription
mvn clean install -Dproduct=brsThe binary and source distributions
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.

...