[YETUS-54] Add Yetus parent POM and top-level POM

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1.0
• Fix Version/s: 0.1.0
• Component/s: Audience Annotations, build
• Assignee: Sean Busbey
• Reporter: Andrew Bayer
• Created: 24/Sep/15 08:13
• Updated: 16/Oct/15 01:02
• Resolved: 16/Oct/15 01:02

Description

So at least for as long as we're using Maven, I'd strongly advise that we not have audience-annotations inherit from hadoop-common's parent POM and instead inherit from a Yetus parent POM. I'd also advise that we follow the same kind of split that Hadoop has, with a yetus-parent POM in a subdirectory, separate from a top-level POM in the root directory. Parent POMs are great for defining things to inherit (versions, dependencies, properties, SCM info, etc) but are crap for aggregation once you try to do things like site generation, javadoc, etc.

Issue Links

• is depended upon by: YETUS-3 update audience annotations for move to yetus tlp
• is related to: YETUS-15 build environment
• is related to: YETUS-6 reorganize repo layout for break from Hadoop code base