I see now why the compilation error happened. To my understanding, it should be Yetus' job to determine the proper dependencies among the modules.
Cheers On Tue, Jan 12, 2016 at 10:53 AM, Allen Wittenauer <[email protected]> wrote: > > > On Jan 12, 2016, at 10:49 AM, Ted Yu <[email protected]> wrote: > > > > I ran the same command locally used by Yetus: > > > > mvn clean test-compile -DskipTests=true > > > > And there was no compilation error. > > A single command doesn’t actually duplicate everything > that Yetus does, however. Without doing a significant amount of work, > probably the easiest thing to do to simulate is going to be: > > 1. Blow away your local maven repo cache > 2. Run that command in the same directory, not from the > root of the source tree > >
