From a1aac04a47b8d0f01afe0e531319137261be98f1 Mon Sep 17 00:00:00 2001
From: James Adams <james.adams@stfc.ac.uk>
Date: Wed, 27 May 2015 15:52:13 +0100
Subject: [PATCH] Run tests to produce metaconfig pan templates

Currently we rely on the unit tests to produce the pan templates as a side effect.

This is indeed ugly, see https://github.com/quattor/maven-tools/issues/40.
---
 src/releasing/releaser.sh | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/src/releasing/releaser.sh b/src/releasing/releaser.sh
index f548093c1d..7bfe5df11c 100755
--- a/src/releasing/releaser.sh
+++ b/src/releasing/releaser.sh
@@ -50,7 +50,14 @@ publish_templates() {
     tag=$2
     cd configuration-modules-$1
     git checkout $tag
-    mvn-c -q clean compile
+    mvn-c clean test
+    mvn-c clean compile
+    # ugly hack
+    if [ -d ncm-metaconfig ]; then
+        cd ncm-metaconfig
+        mvn-c clean test
+        cd ..
+    fi
     components_root=${LIBRARY_CORE_DIR}/components
     metaconfig_root=${LIBRARY_CORE_DIR}/metaconfig
     mkdir -p ${components_root}