[ 
https://issues.apache.org/jira/browse/MINVOKER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958301#comment-17958301
 ] 

Olivier Lamy commented on MINVOKER-56:
--------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-invoker-plugin#331|https://github.com/apache/maven-invoker-plugin/issues/331].
 

> Clone all projects which are locally reachable from the invoked IT project
> --------------------------------------------------------------------------
>
>                 Key: MINVOKER-56
>                 URL: https://issues.apache.org/jira/browse/MINVOKER-56
>             Project: Maven Invoker Plugin (Moved to GitHub Issues)
>          Issue Type: Improvement
>    Affects Versions: 1.2.1
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>            Priority: Major
>             Fix For: 1.3
>
>
> Imagine the following directory structure:
> {noformat}
> ./
>   aggregator/     (references module)
>   module/         (inherits from module-parent)
>   module-parent/
> {noformat}
> Further assume the Invoker Plugin is configured to clone the projects and 
> {{aggregator}} is the only project selected for invocation via 
> {{pomIncludes}}.
> Currently, the plugin will only clone projects which have been matched via 
> the include/exclude patterns. For the above example, this means only 
> {{aggregator}} is cloned. Its invocation will then fail since the other 
> projects (indirectly) referenced by it, namely {{module}} and 
> {{module-parent}}, haven't been cloned.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to