On Thu, Oct 22, 2015 at 1:43 PM, Allen Wittenauer <[email protected]> wrote:
> > On Oct 22, 2015, at 10:25 AM, Tony Kurc <[email protected]> wrote: > > > say I have a project with submodules, project is A, with submodules B and > > D. B has a submodule C, D has a submodule E. A structure similar to this: > > > > A/B/C > > A/D/E > > > > I have a patch that changes C and E and some methods change in E that C > > depends on and there are changes to C that E depends on. When run I run > > test-patch , "Patch maven install fails". I get failures (compilation > > errors) because it looks like C is traversed to and maven is run and > fails > > to compile. It looks like it fails because it is using the pre-patch > > installed jars. I was reading code and maven submodule best practices, > but > > not getting anywhere to get past this. > > > > Is this a use case someone else has working? > > IIRC, by default, test-patch will do everything at root. So if > the maven dependencies are wacky, test-patch will definitely show that type > of behavior. > > HOWEVER! WE GOT YOU COVERED! :D > > What you’re looking for is the module queue that personalities can > use. Take a look at hadoop’s, which is probably overly complicated as an > example, but it does do module re-ordering to make sure the dependencies > are done correctly.
