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

[Sebastian Schuberth (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Schuberth updated SHRINKRES-271:
------------------------------------------
    Description: 
Maven dependency resolution does not seem to be reactor-aware in 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.

  was:
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.



> 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 does not seem to be reactor-aware in 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)