[
https://jira.codehaus.org/browse/MINVOKER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MINVOKER-125:
------------------------------------
Description: Often (may be everytime) groovy scripts (post-build) which are
doing work in relationship with integration-tests must access the *target*
folder to check results etc. But currently i have to hard code the folder
"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 folder. (was: Often (may
be everytime) groovy scripts (post-build) which are doing work in relationship
with integration-tests must access the *target* folder to check results etc.
But currently i have to hard code the folder "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 folder.)
> Global variable about the target folder into the groovy scripts.
> ----------------------------------------------------------------
>
> Key: MINVOKER-125
> URL: https://jira.codehaus.org/browse/MINVOKER-125
> Project: Maven Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Karl-Heinz Marbaise
> Priority: Minor
>
> Often (may be everytime) groovy scripts (post-build) which are doing work in
> relationship with integration-tests must access the *target* folder to check
> results etc. But currently i have to hard code the folder "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 folder.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
