[
https://issues.jboss.org/browse/SHRINKRES-271?page=com.atlassian.jira.plu...
]
Karel Piwko commented on SHRINKRES-271:
---------------------------------------
Just my $0.02, I was thinking at in the past about this problem.
There is a very limited and dirty reactor like functionality in SWR -
https://github.com/shrinkwrap/resolver/blob/f04847288f077f396c2592c07c890....
The problem is, to implement that correctly, you would need to reimplement Maven Reactor.
That's a significant piece of work. Maybe you could just alter current implementation
to handle your specific case?
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.2.3#72005)