sap-jenkins-library/documentation/bin/createDocu.sh

#!/bin/bash

d=$(dirname "$0")
[ !  -z  "$d"  ] &&  d="$d/"

export CLASSPATH_FILE='target/cp.txt'
mvn clean test dependency:build-classpath -Dmdep.outputFile=${CLASSPATH_FILE} > /dev/null 2>&1
groovy  "${d}steps" -in target/trackedCalls.json --out target/performedCalls.json
groovy -cp "target/classes:$(cat $CLASSPATH_FILE)" "${d}createDocu" "${@}"
add scripts (sh, groovy) for generating docu 2018-10-16 13:07:38 +02:00			`#!/bin/bash`

Relocate script files for generting documention 2019-01-09 17:30:22 +02:00			`d=$(dirname "$0")`
			`[ ! -z "$d" ] && d="$d/"`

Create file containing classpath into build dir and not into project root. With this appraoch the root folder get not filled with temporary content. 2019-01-14 09:32:34 +02:00			`export CLASSPATH_FILE='target/cp.txt'`
run the tests (required for getting plugins deps) 2019-05-21 11:53:10 +02:00			`mvn clean test dependency:build-classpath -Dmdep.outputFile=${CLASSPATH_FILE} > /dev/null 2>&1`
run condence steps within createDocu 2019-05-21 12:19:32 +02:00			`groovy "${d}steps" -in target/trackedCalls.json --out target/performedCalls.json`
docu script classpath contains the built classes folder we do not have only groovy script, but also java files inside src folder. Hence we should rely on the target/classes folder in order to see also the compiled java classes, and not only the groovy scripts. 2019-01-11 15:21:00 +02:00			`groovy -cp "target/classes:$(cat $CLASSPATH_FILE)" "${d}createDocu" "${@}"`