WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system using the following commands, building the product and making changes, and then committing your changes back to the source repository. For information on using Subversion, see http://svnbook.red-bean.com.
Checking out the source
You can use the svn checkout command to download the trunk or a specific branch of Developer Studio to the directory you specify. For example:
Trunk: svn checkout https://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/ wso2devstudio
3.5.0 branch: svn checkout https://svn.wso2.org/repos/wso2/branches/tools/eclipse/developer-studio/3.5.0/ wso2devstudio350
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:
[global] http-proxy-host = your.proxy.name http-proxy-port = 3128
Building the product
Following are the commands you can run to create complete release artifacts of WSO2 Developer Studio, including the binary and source distributions.
Before you build:
- Install Maven and JDK. See Installation Prerequisites for compatible versions.
- Set the environment variable
MAVEN_OPTS="-Xms768m -Xmx3072m -XX:MaxPermSize=1200m"to avoid the MavenOutOfMemoryError. - Make sure the build server has an active Internet connection to download dependencies while building.
- Switch to the directory where you checked out Developer Studio before entering these commands.
| This command... | Creates... |
|---|---|
mvn clean install | The binary and source distributions |
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. |
Committing your changes
If you are a committer, you can commit your changes using the following command (SVN will prompt you for your password):
$ svn commit --username your-username -m "A message"