I suspect it's a wider bug than just defaults. IIRC, I also didn't include the nobuild plugin while using it for testing yetus locally yesterday.
On Thu, Oct 22, 2015 at 8:10 PM, Tony Kurc <[email protected]> wrote: > Thanks! > All signs point to me needing to build a personality. > > I wasn't sure if it was a bug or feature. I had been typing it, then forgot > one time, then noticed it did the same exact thing. > > On Thu, Oct 22, 2015 at 8:29 PM, Allen Wittenauer <[email protected]> wrote: > >> >> On Oct 22, 2015, at 5:13 PM, Tony Kurc <[email protected]> wrote: >> > Here is the output that leads me to believe it is changing directories >> and >> > building. >> >> I misspoke earlier (spending too much time on the >> make/cmake/autoconf support!). Maven definitely assumes that modules can >> stand on their own. Here’s the relevant code from maven.sh: >> >> 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…. -- Sean
