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.
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! --Chris Nauroth On 5/13/15, 4:14 AM, "Alan Burlison" <alan.burli...@oracle.com> wrote: >https://issues.apache.org/jira/browse/HADOOP-9279 > >Document the need to build hadoop-maven-plugins for eclipse and separate >project builds > >Although the BUILDING.txt mentions the need to to build >hadoop-maven-plugins for Eclipse, it's actually needed for *all* builds, >even from the top level, otherwise a top-level build will fail with: > >[ERROR] Failed to parse plugin descriptor for >org.apache.hadoop:hadoop-maven-plugins:3.0.0-SNAPSHOT >(/pool1/home/alanbur/bleaklow/bigdata/hadoop/hadoop-maven-plugins/target/c >lasses): >No plugin descriptor found at META-INF/maven/plugin.xml -> [Help 1] > >Manually building hadoop-maven-plugins fixes the problem, but if I'm >reading HADOOP-9279 right it shouldn't be required. What's the correct >course of action here, reopen HADOOP-9279 or log a new bug? If it's the >former I can't see any way of reopening it in JIRA, presumably because >I'm not blessed enough to do so. > >Thanks, > >-- >Alan Burlison >--
