[Chore]: document update and build time optimize

CONTRIBUTING.md

@@ -15,39 +15,39 @@
   ~ limitations under the License.
   -->
 
-# Contributing to Firestorm
-Welcome to [report Issues](https://github.com/Tencent/Firestorm/issues) or [pull requests](https://github.com/Tencent/Firestorm/pulls). It's recommended to read the following Contributing Guide first before contributing. 
+# Contributing to Uniffle
+Welcome to report [Issues](https://github.com/apache/incubator-uniffle/issues) or make [pull requests](https://github.com/apache/incubator-uniffle/pulls). It's recommended to read the following contributing guide first before contributing. 
 
 ## Issues
-We use Github Issues to track public bugs and feature requests.
+We use GitHub Issues to track public bugs and feature requests.
 
 ### Search Known Issues First
-Please search on [report Issues](https://github.com/Tencent/Firestorm/issues) to avoid creating duplicate issue.
+Please search on [Issues](https://github.com/apache/incubator-uniffle/issues) to avoid creating duplicate issues.
 
 ### Reporting New Issues
 * Be sure to include a title and clear description, as much relevant information as possible.
-* A code sample or an executable test case demonstrating is high recommended.
+* A code sample or an executable test case demonstrating is highly recommended.
 
 ## Pull Requests
 * We use master branch as our developing branch.
 * Do not commit/push directly to the master branch. Instead, create a fork and file a pull request.
 * When maintaining a branch, merge frequently with the master.
 * When maintaining a branch, submit pull requests to the master frequently.
 * If you are working on a bigger issue try to split it up into several smaller issues.
-* We reserve full and final discretion over whether or not we will merge a pull request. Adhering to these guidelines is not a complete guarantee that your pull request will be merged.
+* We reserve full and final discretion over whether we will merge a pull request. Adhering to these guidelines is not a complete guarantee that your pull request will be merged.
 
 ### Make Pull Requests
-The code team will monitor all pull request, we run some code check and test on it. After all tests passed, we will accecpt this PR. But it won't merge to `master` branch at once, which have some delay.
+The code team will monitor all pull requests, we run some code check and test on it. After all tests passed and all the review comments addressed, we will accept the PR.
 
 Before submitting a pull request, please make sure the followings are done:
 
 1. Fork the repo and create your branch from `master`.
 2. Update code or documentation if you have changed APIs.
 3. Add the copyright notice to the top of any new files you've added.
-4. Check your code lints and checkstyles.
+4. Check your code lints and checkstyle.
 5. Test and test again your code.
 
 ## Code Style Guide
-Use [Code Style](https://github.com/Tencent/Firestorm/blob/master/checkstyle.xml) for Java.
+Use [Code Style](https://github.com/apache/incubator-uniffle/blob/master/checkstyle.xml) for Java.
 
 * 2 spaces for indentation rather than tabs

README.md

@@ -64,6 +64,7 @@ Note: To support dynamic allocation, the patch(which is included in client-spark
 Current support Hadoop 2.8.5's MapReduce framework.
 
 ## Building Uniffle
+> note: currently Uniffle requires JDK 1.8 to build, adding later JDK support is on our roadmap.
 
 Uniffle is built using [Apache Maven](https://maven.apache.org/).
 To build it, run:

pom.xml

@@ -322,6 +322,12 @@
         <artifactId>hadoop-common</artifactId>
         <version>${hadoop.version}</version>
         <scope>${hadoop.scope}</scope>
+        <exclusions>
+          <exclusion>
+            <groupId>net.minidev</groupId>
+            <artifactId>json-smart</artifactId>
+          </exclusion>
+        </exclusions>
       </dependency>
       <dependency>
         <groupId>org.apache.hadoop</groupId>