Here's the direct links for both POMs morseflash-lib/pom.xml<https://github.com/jayway/maven-android-plugin-samples/blob/master/morseflash/morseflash-lib/pom.xml> morseflash-app/pom.xml<https://github.com/jayway/maven-android-plugin-samples/blob/master/morseflash/morseflash-app/pom.xml>
On Thu, Mar 20, 2014 at 2:59 PM, William Ferguson < [email protected]> wrote: > Martin, > > https://github.com/jayway/maven-android-plugin-samples > > In particular the morseflash module which has: > > - morse-flash-lib > - morse-flash-app (which is dependent on morse-flash-lib) > > > William > > > > On Thu, Mar 20, 2014 at 10:28 AM, Martin Gainty <[email protected]>wrote: > >> William- >> >> Can you show us the pom for both: >> Parent (X?) >> >> Dependency (Y?) >> >> >> >> >> >> > Date: Thu, 20 Mar 2014 09:55:31 +1000 >> > Subject: maven-dependency-tree reactor resolution >> > From: [email protected] >> > To: [email protected] >> > CC: [email protected] >> > >> > Hi, >> > >> > I have a plugin that uses the maven-dependency-tree component to resolve >> > project dependencies in a LifeCycleParticipant. (We need early access to >> > deps because we need to modify the compile classpath). >> > >> > But I'm finding that with a clean repository, in a multi-module project >> > with modules X and Y-depends-on-X that the DependencyGraphBuilder is >> > throwing a DependencyGraphBuilderException when trying to resolve >> > Y-depends-on-X. It says that it cannot find X. >> > >> > So it appears that the maven-dependency-tree is only using information >> from >> > the repository and not the reactor. >> > >> > Is that expected? >> > Is there anyway that I can get MDT to resolve from the reactor? >> > Is there another approach that I should be taking to ensure that >> resolution >> > looks in the reactor? >> > >> > NB I need to support both maven 3.0 and 3.1 which is why we are using >> MDT >> > to provide a level of abstraction above the 2 differing Aether >> > implementations. >> > >> > William >> >> > >
