In GitHub, the WSO2 source code is organized into separate repositories, and each WSO2 product is built using several of these repositories. Therefore, if you are interested in editing the source code and building a customized product, you need to first identify the Git repositories that you require.
Feature repositories: A feature repository consists of the source code relevant to a particular component. Each WSO2 product release is built using combinations of these component feature repositories. Therefore, if you want to do modifications to a particular function in a product, you need to clone the Git repositories relevant to that function.
For example, listed below are the main component Git repositories (but not all) that are used for WSO2 AS 5.3.0 release. The Tag ID indicates the tag from the repository Note that each repository will also consist of Tag IDs, which correspond to the tag that was used for the a particular product release. If If you want to know more about other component repositories and the tags used for a product release, send an email to firstname.lastname@example.org.
Git Repository Name Repository URL Tag for AS 5.3.0 Release
https://github.com/wso2/carbon4-kernel.git v4.4.1 carbon-commons https://github.com/wso2/carbon-commons.git v4.4.7 carbon-identity https://github.com/wso2/carbon-identity.git v4.5.5 carbon-registry https://github.com/wso2/carbon-registry.git v4.4.8 carbon-multitenancy https://github.com/wso2/carbon-multitenancy.git v4.4.3 carbon-deployment https://github.com/wso2/carbon-deployment.git v4.5.2
Product-build repository: A product-build repository consists of the build scripts and profiles that are used for building the product. It also includes the Integration test cases.
For example, given below is the product repository for the WSO2 AS 5.3.0 release. When you build this product You can simply clone this repository tag to your computer and build it to get a standard product pack. When you build a product-build repository, all the component repositories that are required for the AS 5.3.0 release (such as the ones listed above) that product release will be automatically fetched from Nexus. Therefore, you can simple clone this repository tag to your computer and build it to get a standard product pack. See See the topic on Using Maven to build Git repositories.
Git Repository Name Repository URL Tag for AS 5.3.0 Release product-as https://github.com/wso2/product-as.git v5.3.0
Cloning a Git repository
Given below are the steps that you need to follow in order to clone a Git repository to your computer.
Clone the repository, so that the files that are in the WSO2 Git repository are available on your computer:
git clone <DEPENDENT_REPOSITORY_URL> <LOCAL_FOLDER_PATH>
For example, clone the
carbon-commonsrepository, which is in the WSO2 Git repository, to a folder named
CC_SOURCE_HOMEon your computer:
git clone https://github.com/wso2/carbon-commons.git /Users/testuser/Documents/CC_SOURCE_HOME
Navigate to the folder in your computer to which the code base is cloned:
Clone the dependent repository tag that corresponds to the version of the code base:
git checkout -b <REMOTE_BRANCH/TAG> <LOCAL_BRANCH>
The local branch name should be identical to the remote branch name.
For example, if you want to download the
carbon-commonsrepository tag that was used for the WSO2 AS 5.3.0 release, you need to clone the v4.4.7 tag:
git checkout -b v4.4.7 v4.4.7
As explained above in the section on identifying WSO2 Git repositories, you can easily build a product pack by building the product-build Git repository on your computer. However, if you have modified any of the component-level repositories feature repositories that are used for this product, you need to first build those component feature repositories before building the product-build repository. Given below are the steps you need to follow.
Once you have built the feature repositories, build the product-build repository that you have cloned to your computer.
When you build the product repository, Maven will first check in the local Maven repository on your computer and fetch the repositories that you built in Step 1. Maven will then fetch the remaining dependent repositories from Nexus. This process will give you a new product pack with your changes.
You can find the new binary pack (ZIP file) , in in the
Use one of the following Maven commands to build your repositories:
The binary and source distributions.
|The binary and source distributions, without running any of the unit tests.|
|The binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you have already built the source at least once.|