From c09a5dbe1737c62c335e158e50cf2c2de5a17a71 Mon Sep 17 00:00:00 2001 From: r0bb3n Date: Sun, 25 Apr 2021 10:36:31 +0200 Subject: [PATCH] docs: why java 11? --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 22abb3d..a2ba8eb 100644 --- a/README.md +++ b/README.md @@ -19,6 +19,7 @@ There a three modes supported: ## Prerequisites * Java 11 + * see section [Why Java 11?](#why-java-11) for details * SonarQube (depends on mode) * integrated: 5.3+ * simple: 5.4+ @@ -77,10 +78,19 @@ mvn sonar-quality-gate:check -Dsonar-quality-gate.branch=develop | `sonar-quality-gate.checkTask.interval.s` | How many seconds to wait between two requests when retrieving task details
(default: `5`) | integrated | [sonar-analysis-param]: https://docs.sonarqube.org/latest/analysis/analysis-parameters/ + [sonar-web-api-auth]: https://docs.sonarqube.org/latest/extend/web-api/ ## Internals +### Why Java 11? + +**TL;DR** usage of HttpClient (`java.net.http.HttpClient`) + +Thinking about also supporting Java 8 led to the conclusion, that this would require relying on at least one additional +dependency (to maintain) for HTTP calls (e.g. Apache HttpClient), which is solved out-of-the-box in Java 11+ by simply +using `java.net.http.HttpClient`. Therefore, I decided to not support Java 8. + ### Calling SonarQube Web API #### Project Status