You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/04/20 06:42:00 UTC
[jira] [Commented] (MINVOKER-125) Global variable about the target folder into the groovy scripts.
[ https://issues.apache.org/jira/browse/MINVOKER-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524764#comment-17524764 ]
Slawomir Jaranowski commented on MINVOKER-125:
----------------------------------------------
To resolve this issue we will need evaluate properties like project.build.directory for test project.
It will be too complicate from invoker perspective.
> Global variable about the target folder into the groovy scripts.
> ----------------------------------------------------------------
>
> Key: MINVOKER-125
> URL: https://issues.apache.org/jira/browse/MINVOKER-125
> Project: Maven Invoker Plugin
> Issue Type: New Feature
> 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
(v8.20.7#820007)