[
https://issues.apache.org/jira/browse/MINVOKER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958413#comment-17958413
]
Olivier Lamy commented on MINVOKER-161:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#428|https://github.com/apache/maven-invoker-plugin/issues/428].
> Full path names not recognized
> ------------------------------
>
> Key: MINVOKER-161
> URL: https://issues.apache.org/jira/browse/MINVOKER-161
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.8
> Environment: windows
> Reporter: Gregory Baumgardner
> Priority: Minor
>
> I am trying to run a "common" pre-build hook script across multiple
> executions of the invoker plugin. This seems like a trivial thing to do,
> given the pluginManagement configuration concept, but does not work because
> the script is treated as a relative path. I cannot use a full path to the
> script at all, nor can I guarantee that the relative path to the script is
> the same for each project I am trying to invoke. What I found through
> debugging the code is that the pre-hook (and presumably post-hook) scripts
> are considered relative to the basedir of the project that will be invoked,
> and not the basedir for the plugin configuration project. I suppose that
> makes sense, but it leaves me no good way that I can see to reuse the script.
> An easy fix here would be to recognize full path names when you see one, and
> use that instead of adding it to the basedir. See example below.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
