I usually tell people starting fresh to do "mvn clean install -Pnative -DskipTests" as a first step. That's a good validation of your build environment, and it will put a SNAPSHOT version of each sub-module into your local Maven repository. After that, you can do smaller incremental builds by cd'ing into hadoop-hdfs or hadoop-yarn-server-nodemanager or anything else and running things like "mvn test" for just that sub-module.
--Chris Nauroth On 5/13/15, 9:28 AM, "Alan Burlison" <alan.burli...@oracle.com> wrote: >On 13/05/2015 16:53, Chris Nauroth wrote: > >> Last time I checked, this was particular to "mvn compile" and would not >> occur for other kinds of builds from the root of the source tree like >>"mvn >> test" or "mvn package". This is a Maven behavior that is unavoidable >> unless we pull hadoop-maven-plugins out into its own project separate >>from >> the Hadoop source tree, which is something the community already decided >> against. We can only document the behavior. > >Thanks for the explanation, I've added a comment to HADOOP-9279 to that >effect. What's the best recommended target for someone to use when >starting from scratch, test? > >> Please feel free to file a new issue if you'd like to see this clarified >> in BUILDING.txt. We'd welcome a patch if you want to provide one. >>Thanks! > >Yes, I'll do that. > >-- >Alan Burlison >--
