[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-271) Maven dependency resolution is not reactor-aware

[Matous Jobanek (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406379#comment-13406379 ] 

Matous Jobanek commented on SHRINKRES-271:
------------------------------------------

Hi,
unfortunately, this is not possible. According to the project structure you have sent, the `jgnash-resources` is another module of the whole project. So, technically, If you ran the `mvn dependency:tree` from this module using your command line, it would fail as it wouldn't be able to find the jar files in your local repository. As this is not supported by Maven itself then it is impossible to support it by Shrinkwrap Resolver. 

> Maven dependency resolution is not reactor-aware
> ------------------------------------------------
>
>                 Key: SHRINKRES-271
>                 URL: https://issues.jboss.org/browse/SHRINKRES-271
>             Project: ShrinkWrap Resolvers
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 2.2.6
>         Environment: Windows 10 64-bit
>            Reporter: Sebastian Schuberth
>
> Maven dependency resolution doe snot seem to be reactor-aware n the sense that inter-module dependencies in a multi-module project are not resolved properly unless they are manually installed in the local Maven cache.
> The general problem when using the Maven command line tool is well described at http://stackoverflow.com/questions/1677473/maven-doesnt-recognize-sibling-modules-when-running-mvn-dependencytree.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)