That's it... and also note that while Maven complains if the pom at the specified <relativePath> is not the parent, it will build correctly ... just resolving the parent from the local repository and not from the disk.
On 16 June 2014 06:05, Barrie Treloar <[email protected]> wrote: > On 16 June 2014 14:12, Stephen Connolly <[email protected]> > wrote: > > > On Sunday, 15 June 2014, Mark Derricutt <[email protected]> wrote: > > > > > So if I have two modules that are interdependent on in-progress > changes, > > > how does one build/test the dependant one. > > > > > > Note - reactor builds and multi-modules builds are out of the question > - > > > the above modules are in separate git repositories and there's no way > to > > > create a "fake reactor" setup - i.e. a separate pom.xml just listing > > > <module/> elements ( maven complains when that pom is not the parent ). > > > > > > Even if the local aggregator does something like > > > > <module>../foo</module> > > > A link to a blog post or more detail might be useful for those still > learning. > > I'm pretty sure I know this to look like > ROOT/ > - aggregator > - pom.xml (reference modules ../projectA and ../projectB) > - projectA > - projectB > > But its not something I do, and I'm hoping I got it right from Maven > experience :) > > This is where the vaoporware "Magic Checkout" plugin that Kristian has > mentioned would be useful. > This plugin would automatically change a released dependency to its > snapshot version, check it out, and update/create the aggregator project to > reference the checked out version. >
