[MINVOKER-125] Global variable about the target directory into the groovy scripts

**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** opened **[MINVOKER-125](https://issues.apache.org/jira/browse/MINVOKER-125?redirect=false)** and commented

Often (may be everytime) groovy scripts (post-build) which are doing work in relationship with integration-tests must access the **target** directory to check results etc. But currently i have to hard code the directory "target" by contrast in the pom.xml there already exists a good replacement for that ${project.build.directory} so it would be very helpful to have an context information like "target" which represents the target directory.

---

**Affects:** 1.5

**Issue Links:**
- [MINVOKER-141](https://issues.apache.org/jira/browse/MINVOKER-141) passing own properties to all scripts

Start by tracing how post-build Groovy scripts receive context and how the existing ${project.build.directory} value is represented in the Maven configuration. The issue is done when integration-test scripts can access the target directory through context instead of hard-coding "target"; review MINVOKER-141 for related property-passing behavior.

Written by the indexing model from the issue text.