From d60853341b9ad657fb1541e2625dd42400d38c18 Mon Sep 17 00:00:00 2001
From: Julien HENRY <julien.henry@sonarsource.com>
Date: Mon, 8 Dec 2014 11:12:15 +0100
Subject: [PATCH] Update documentation of PostJob extension

---
 .../src/main/java/org/sonar/api/batch/PostJob.java       | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/sonar-plugin-api/src/main/java/org/sonar/api/batch/PostJob.java b/sonar-plugin-api/src/main/java/org/sonar/api/batch/PostJob.java
index 52eff7acc68..a01a83178e0 100644
--- a/sonar-plugin-api/src/main/java/org/sonar/api/batch/PostJob.java
+++ b/sonar-plugin-api/src/main/java/org/sonar/api/batch/PostJob.java
@@ -23,11 +23,10 @@ import org.sonar.api.BatchExtension;
 import org.sonar.api.resources.Project;
 
 /**
- * PostJobs are executed when project is analysed.
- * <p/>
- * <p>
- * Note : executed only on root project, not on modules.
- * </p>
+ * PostJobs are executed at the very end of batch analysis. A PostJob can't do any modification
+ * since everything is already computed (issues, measures,...). <br/>
+ * WANRING: Do not rely on the fact that analysis results are available on server side. Even if it is true
+ * for now (synchronous storage) it will become an asynchronous processing on server side in 5.x series.
  *
  * @since 1.10
  */
-- 
2.39.5