How-to-build.md 6.4 KB
Newer Older
wu-sheng's avatar
wu-sheng 已提交
1
# How to build project
2
This document helps people to compile and build the project in your maven and set your IDE.
wu-sheng's avatar
wu-sheng 已提交
3

4 5 6 7 8
## Build Project
**Because we are using Git submodule, we recommend don't use `GitHub` tag or release page to download source codes for compiling.**

### Build from GitHub
1. Prepare git, JDK8 and maven3
9 10
1. `git clone https://github.com/apache/skywalking.git`
1. `cd skywalking/`
11
1. Switch to the tag by using `git checkout [tagname]` (Optional, switch if want to build a release from source codes)
wu-sheng's avatar
wu-sheng 已提交
12 13
1. `git submodule init`
1. `git submodule update`
14
1. Run `./mvnw clean package -DskipTests`
15
1. All packages are in `/dist` (.tar.gz for Linux and .zip for Windows).
16

wu-sheng's avatar
wu-sheng 已提交
17 18 19 20 21
### Build from Apache source code release
- What is `Apache source code release`?

For each official Apache release, there is a complete and independent source code tar, which is including all source codes. You could download it from [SkyWalking Apache download page](http://skywalking.apache.org/downloads/). No git related stuff required when compiling this. Just follow these steps.

22
1. Prepare JDK8 and maven3
23
1. Run `./mvnw clean package -DskipTests`
wu-sheng's avatar
wu-sheng 已提交
24
1. All packages are in `/dist`.(.tar.gz for Linux and .zip for Windows).
wu-sheng's avatar
wu-sheng 已提交
25

26 27 28 29 30
### Advanced compile
SkyWalking is a complex maven project, including many modules, which could cause long compiling time. 
If you just want to recompile part of the project, you have following options
- Compile agent and package
>  ./mvnw package -Pagent,dist
31 32 33 34 35

or

> make build.agent

36 37
- Compile backend and package
>  ./mvnw package -Pbackend,dist
38 39 40 41 42

or

> make build.backend

43 44 45
- Compile UI and package
>  ./mvnw package -Pui,dist

46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61
or

> make build.ui


### Build docker images
We can build docker images of `backend` and `ui` with `Makefile` located in root folder.

- Build all docker images
> make docker.all

- Build oap server docker image
> make docker.oap

- Build ui docker image
> make docker.ui
62

63 64 65
`HUB` and `TAG` variables ares used to setup `REPOSITORY` and `TAG` of a docker image. To get
a oap image with name `bar/oap:foo`, run the following command
> HUB=bar TAG=foo make docker.oap
66

wu-sheng's avatar
wu-sheng 已提交
67
## Setup your IntelliJ IDEA
D
Daming 已提交
68 69
**NOTICE**: If you clone the codes from GitHub, please make sure that you had finished step 1 to 7 in section **[Build from GitHub](#build-from-github)**, if you download the source codes from the official website of SkyWalking, please make sure that you had followed the steps in section **[Build from Apache source code release](#build-from-apache-source-code-release)**.

wu-sheng's avatar
wu-sheng 已提交
70
1. Import the project as a maven project
71
1. Run `./mvnw compile -Dmaven.test.skip=true` to compile project and generate source codes. Because we use gRPC and protobuf.
wu-sheng's avatar
wu-sheng 已提交
72
1. Set **Generated Source Codes** folders.
73
    * `grpc-java` and `java` folders in **apm-protocol/apm-network/target/generated-sources/protobuf**
X
XiaoFu 已提交
74
    * `grpc-java` and `java` folders in **oap-server/server-core/target/generated-sources/protobuf**
wu-sheng's avatar
wu-sheng 已提交
75
    * `grpc-java` and `java` folders in **oap-server/server-receiver-plugin/receiver-proto/target/generated-sources/protobuf**
wu-sheng's avatar
wu-sheng 已提交
76
    * `grpc-java` and `java` folders in **oap-server/exporter/target/generated-sources/protobuf**
77
    * `grpc-java` and `java` folders in **oap-server/server-configuration/grpc-configuration-sync/target/generated-sources/protobuf**
wu-sheng's avatar
wu-sheng 已提交
78
    * `antlr4` folder in **oap-server/generate-tool-grammar/target/generated-sources**
79 80
    
## Setup your Eclipse IDE
D
Daming 已提交
81 82
**NOTICE**: If you clone the codes from GitHub, please make sure that you had finished step 1 to 7 in section **[Build from GitHub](#build-from-github)**, if you download the source codes from the official website of SkyWalking, please make sure that you had followed the steps in section **[Build from Apache source code release](#build-from-apache-source-code-release)**.

83
1. Import the project as a maven project
84
2. For supporting multiple source directories, you need to add the following configuration in `skywalking/pom.xml` file:
85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147
```
<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>build-helper-maven-plugin</artifactId>
    <version>1.8</version>
    <executions>
        <execution>
            <id>add-source</id>
            <phase>generate-sources</phase>
            <goals>
                <goal>add-source</goal>
            </goals>
            <configuration>
                <sources>
                    <source>src/java/main</source>
                    <source>apm-protocol/apm-network/target/generated-sources/protobuf</source>
                    <source>apm-collector/apm-collector-remote/collector-remote-grpc-provider/target/generated-sources/protobuf</source>
               </sources>
            </configuration>
        </execution>
    </executions>
</plugin>
```
3. Add the following configuration under to let eclipse's M2e plug-in supports execution's solution configuration
```
<pluginManagement>
    <plugins>
    <!--This plugin's configuration is used to store Eclipse m2e settings 
    only. It has no influence on the Maven build itself. -->
        <plugin>
            <groupId>org.eclipse.m2e</groupId>
            <artifactId>lifecycle-mapping</artifactId>
            <version>1.0.0</version>
            <configuration>
                <lifecycleMappingMetadata>
                    <pluginExecutions>
                        <pluginExecution>
                            <pluginExecutionFilter>
                                <groupId>org.codehaus.mojo</groupId>
                                <artifactId>build-helper-maven-plugin</artifactId>
                                <versionRange>[1.8,)</versionRange>
                                <goals>
                                    <goal>add-source</goal>
                                </goals>
                            </pluginExecutionFilter>
                        </pluginExecution>
                    </pluginExecutions>
                </lifecycleMappingMetadata>
            </configuration>
        </plugin>
    </plugins>
</pluginManagement>
```
4. Adding Google guava dependency to apm-collector-remote/collector-remote-grpc-provider/pom.xml files
```
<dependency>
   <groupId>com.google.guava</groupId>
   <artifactId>guava</artifactId>
   <version>24.0-jre</version>
</dependency>
```
5. Run `./mvnw compile -Dmaven.test.skip=true`
6. Run `maven update`. Must remove the clean projects item before maven update(This will be clear the proto conversion Java file generated by the complie)
148
7. Run `./mvnw compile` compile collector-remote-grpc-provider and apm-protocol
149
8. Refresh project