I think what I'll do is make a small project which is built similarly and be easier to diagnose whether I'm doing something wrong or test-patch is doing something I'm not expecting.
On Thu, Oct 22, 2015 at 2:51 PM, Sean Busbey <[email protected]> wrote: > do things work correctly if you start at the top and manually run: > > mvn --projects C,E --also-make test > > On Thu, Oct 22, 2015 at 12:25 PM, 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? > > > > Tony >
