[
https://issues.apache.org/jira/browse/MINVOKER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643922#comment-16643922
]
Christopher Tubbs commented on MINVOKER-243:
--------------------------------------------
[~rfscholte], yes. In this case, the transitive dependency is a sibling module
in a multi-module project.
Example:
module A: depends on commons-configuration
module B: depends on A and commons-io
module C: maven plugin configured with invoker for ITs, depends on B
{{invoker:install}} in module C should install the jar from module B, and also
the jar from module A (because it is a transitive dependency of B), but not
commons-io or commons-configuration.
Version 3.0.1 works fine, but 3.1.0 fails to install module A, instead only
installing module B.
> invoker:install doesn't copy transitive dependencies anymore (as of 3.1.0)
> --------------------------------------------------------------------------
>
> Key: MINVOKER-243
> URL: https://issues.apache.org/jira/browse/MINVOKER-243
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Christopher Tubbs
> Priority: Blocker
>
> Something seems to have broken between 3.0.1 and 3.1.0, as the install goal
> no longer copies transitive dependencies to the localRepositoryPath as it did
> in version 3.0.1.
> This is very problematic, because if the artifacts are not in the
> localRepositoryPath, the invoked project will try to download them from a
> remote repository, which isn't possible for SNAPSHOT versions (such as those
> in a sibling module in a multi-module project). This can make it difficult to
> even build a multi-module project, unless the invoked task is skipped and the
> sibling module can be published to a remote snapshot repository temporarily,
> and then the build re-executed normally. (Saw this happen in Apache Accumulo
> after upgrading to apache-21.pom)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
