[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-271) Maven dependency resolution is not reactor-aware
[
https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plu...
]
Sebastian Schuberth edited comment on SHRINKRES-271 at 5/22/18 2:30 PM:
------------------------------------------------------------------------
Turns out there's no need to reimplement the Maven Reator to be able to resolve
inter-module dependencies. Instead you can use the trick from our [OSS Review Toolkit
project|https://github.com/heremaps/oss-review-toolkit] to create a ["fake"
LocalRepositoryManager|https://github.com/heremaps/oss-review-toolkit/blo...]
that pretends that the POM files of the currently analyzed project are available in the
local repository.
was (Author: sschuberth):
Turns out there's no need to reimplement the Maven Reator to be able to resolve
inter-module dependencies. Instead you can use the trick from our [OSS Review Toolkit
project|https://github.com/heremaps/oss-review-toolkit] to create [a "fake"
LocalRepositoryManager|https://github.com/heremaps/oss-review-toolkit/blo...]
that pretends that the POM files of the currently analyzed project are available in the
local repository.
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....
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)