From d80e92df2dba626b5e839cf3c8ad730e3a39f82a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Herv=C3=A9=20Boutemy?= Date: Sun, 18 Aug 2019 10:16:07 +0200 Subject: [PATCH] details on expected failure (typically on ASF Jenkins) --- its/src/site/apt/index.apt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/its/src/site/apt/index.apt b/its/src/site/apt/index.apt index 44951223c3..8f4c4ab355 100644 --- a/its/src/site/apt/index.apt +++ b/its/src/site/apt/index.apt @@ -54,4 +54,10 @@ Maven Core ITs So some care needs to be taken when introducing new dependencies into the ITs themselves or the support plugins. Many times the failures that we encounter are discrepancies between actual artifact consumption required and - what is populated during bootstraping. + what is populated during bootstrapping. When forgetting, typical failures will give following traces in log: + +------- +[INFO] Downloading from central: file:target/null/... +... +[ERROR] Failed to execute goal ... (...) on project ...: ... Could not find artifact ... in central (file:target/null) -> [Help 1] +-------