On Thu, Oct 22, 2015 at 7:29 PM, Allen Wittenauer <[email protected]> wrote: > > > for module in ${CHANGED_MODULES}; do > # shellcheck disable=SC2086 > personality_enqueue_module ${module} > done > > This enqueues each module independently. > >> If I apply the patch and run mvn clean install, it succeeds. Is >> it possible the reactor build order *must* be the same after a patch? > > Given the above, test-patch mostly ignores the reactor build order. > For maven, at least today, if you always want to build from the root of your > project, you’ll need to build a personality that has a custom > personality_modules. > > BTW, it’s interesting that you stumbled upon another bug… maven > wasn’t in the plug-in list but still got executed! That’s a bug with > defaults….
sounds like I should file an improvement bug, since maven could take care of properly ordering things for us instead of having to rely on personalities. hurm... would effectively need to ask the build system "which module is this file in", which sounds non-trivial.
