...
Build from source Anchor source source
| source | |
| source |
WSO2 invites you to contribute by checking out the source from the Subversion (SVN) source control system using the following commands. This project uses Subversion to manage its source code. Instructions on Subversion can be found at For information on using Subversion, see http://svnbook.red-bean.com .
The WSO2 API Manager release 1.4.0
You can download the complete WSO2 Carbon platform, which is recommended if you intend to modify the source. You can check out the complete source anonymously from SVN with the following commands (note that this version of the API Manager is based on Carbon 4.0.7.
Anonymous Checkout
The complete source including the Carbon platform can be checked out anonymously from SVN with this command:
...
.5). The Carbon project comes in three sub projects: Orbit, Kernel, and Platform. Download and build them in that particular order.
Orbit:
$ svn checkout ...
https://svn.wso2.org/repos/wso2/carbon/...
orbit/tags/4.1.0...
wso2carbon
Kernel:
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/tags/4.1.0 wso2carbon
Platform:
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/platform/tags/4.1.0/ wso2carbon
Following are the commands you can run to create complete release artifacts of WSO2 API Manager, including the binary and source distributions. If you only want to build the API Manager, you have to always use the option "use the -Dproduct=apimgt option as shown. If you want to build the entire Carbon core project, omit the -Dproduct=apimgt "option.
| mvn clean install -Dproduct=apimgt | To create the complete release artifacts of the product including the binary and source distributions. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=apimgt | To create the complete release artifacts of the product including the binary and source distributions, without running any of the unit tests. |
| mvn clean install -Dmaven.test.skip=true -Dproduct=apimgt -o | To create the complete release artifacts of the product including 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. |
Developer Access
Everyone can access the Subversion repository via HTTPS, but Committers must checkout via HTTPS. The Carbon framework related source code can be checked out using the following commands.
| Code Block |
|---|
$ svn checkout https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0 wso2carbon |
The Carbon core project is the root project of the OSGi platform on which the Java product stack is built. The Carbon components contain all the components not just the API Manager specific ones. Therefore, you need to build just the set of components required by the API Manager, using the following command:
| Code Block |
|---|
$ mvn clean install -Dproduct=apimgt |
...
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"
Access through a
...
firewall
If you are behind a corporate firewall which that is blocking http HTTP access to the Subversion repository, you can try the developer connection:
...
$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbonAccess through a
...
proxy
The Subversion client can be configured to access through a proxy.
1) 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%")
2) There are comments in the file explaining 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.
Example : Edit the ' servers ' file and add something similar to:
...