[BIGTOP-757] Install ZooKeeper jars into the local Maven cache

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Assignee: Roman Shaposhnik
• Reporter: Andrew Kyle Purtell
• Created: 19/Oct/12 18:31
• Updated: 21/Jun/13 23:55
• Resolved: 22/Oct/12 19:52

Description

The majority of Bigtop components use Maven as their build system, and Bigtop do-component-build scripts invoke their 'install' target, which populates the local Maven cache with the resulting artifacts. A few projects like ZooKeeper still use Ant, so this doesn't happen for those cases. If one specifies a nonrelease version of ZooKeeper, for example as a GitHub download by SHA, then any dependent component will fail to build without some kind of external action. It is reasonable and convenient, and consistent with what happens regards other components, to put the results of ZooKeeper builds into the local Maven cache.