From 583f6fca08ae423f7d5acb53698aee82b66085f9 Mon Sep 17 00:00:00 2001
From: Dominic Schabel <dominic.schabel@bosch-si.com>
Date: Fri, 26 Oct 2018 15:55:40 +0200
Subject: [PATCH] Allure report timeout fixed

Signed-off-by: Dominic Schabel <dominic.schabel@bosch-si.com>
---
 pom.xml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/pom.xml b/pom.xml
index ca7bf48e0..156ee0030 100644
--- a/pom.xml
+++ b/pom.xml
@@ -399,12 +399,11 @@
                <artifactId>maven-surefire-plugin</artifactId>
                <version>${maven.surefire.plugin.version}</version>
                <configuration>
-
                   <systemPropertyVariables>
-                    <!-- Set output directory according to allure-framework recommendation -->
+                     <!-- Set output directory according to allure-framework recommendation -->
                      <allure.results.directory>${project.build.directory}/allure-results</allure.results.directory>
                      <!-- Bugfix for timeout. See https://github.com/allure-framework/allure-maven/issues/59 -->
-                     <allure.report.timeout>600</allure.report.timeout>
+                     <allure.serve.timeout>650</allure.serve.timeout>
 	              </systemPropertyVariables>
                   <reuseForks>true</reuseForks>
                   <forkCount>${surefire.forkcount}</forkCount>