[
https://jira.codehaus.org/browse/MINVOKER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336162#comment-336162
]
Gregory Baumgardner commented on MINVOKER-161:
----------------------------------------------
Set up the projects as follows:
pom.xml
|
|-child/pom.xml
| |
| |-gchild/pom.xml
|
|-src/scripts/prebuild.gsh
If I want to have the parent pom.xml configured to invoke both child pom.xml
and gchild pom.xml, then how to I point to the prebuild.gsh script in a common
way? I mean, I know I can have two separate executions and re-specify the
config both times, but not that this is a simplified view and my real example
has around 8 or so different projects to exec from a common place. It is
somewhat aggravating having to repeat the same information multiple times in a
POM.
> Full path names not recognized
> ------------------------------
>
> Key: MINVOKER-161
> URL: https://jira.codehaus.org/browse/MINVOKER-161
> Project: Maven Invoker Plugin
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
