Hi, Carl Steinbach. I think I understand what's going wrong with fresh imports of the project, and I'm attaching a patch that attempts to fix it. Would you mind trying out this patch in your environment to see if it works for you?
Here is a summary of what I did:
- I changed BUILDING.txt to state that m2eclipse is required, that you should do an mvn install of the whole Hadoop project (not just hadoop-maven-plugins), and that you should import by clicking File -> Import -> Maven -> Existing Maven Projects. Once I did it this way, a fresh import showed ~100 errors.
- hadoop-common still had some errors for missing compiled protoc test sources. This was because the pom.xml was not specifying generated-test-sources/java as a source directory. I added a call to build-helper-maven-plugin to set that up correctly. This eliminated ~40 errors for me.
- m2eclipse didn't know how to handle the goals in our custom Maven plugin for calling protoc and generating version info. I updated the top-level pom.xml to run the protoc goal during an Eclipse build and ignore the version-info goal. This eliminated nearly all of the remaining ~60 errors.
After all of that, a fresh import still gives me one error:
Project 'hadoop-streaming' is missing required source folder: '/Users/chris/git/hadoop-common/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/conf'
It appears that Eclipse doesn't like us to have a test resource pointing at a path outside of the module. I'm not yet sure how to fix this one (other than just copying the file we need out of hadoop-yarn-server-resourcemanager into hadoop-streaming, but then we'd have a double-maintenance issue). It doesn't appear to be fatal though.
I'm curious to see if these fixes address all of the problems that you saw. Thanks!