* Make use of multi-thread builds of maven
* Bump up maven version to get rid of parallel build bug
* Apply the same to E2E tests
* Apply the same to JavaDoc task
* Revert E2E settings
* Add maven tuning opts
* Increase maven fork process memory
* Change OAL generator tool to runtime.
Step 1. change project structure. API links and maven pom.
* Part of metrics class generation
* Metrcis class generated.
* Set up the basic structure of new OAL engine.
* Finish metrics generation.
* Support dispatcher generation.
* Format codes.
* Generate dispatcher all methods.
* Implement disable in hardcode.
* Clear up
* Fix compile startup.
* Update license and document of new OAL engine.
* Fix rat.
* Disable class output in default
* Copy from @kezhenxu94 's test PR, https://github.com/apache/skywalking/pull/3110
* Wait for the mount command to finish
e2e test setup. cc @hanahmily @peng-yongsheng @IanCao @zhaoyuguang @JaredTan95
# e2e test case
One single standalone Spring service, accessing H2 database. This service has been installed the agent.
OAP runs in single mode with H2 storage too.
The e2e test will verify the results through GraphQL query
1. Traces exist.
2. Service/Service Instance/Endpoint exist and have expected metrics.
3. Topology exists and match expected.
kezhenxu94
吴晟 Wu Sheng
kezhenxu94