[GOSSIP-46] Boilder Plate cleanup

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.1.3
• Assignee: Edward Capriolo
• Reporter: Edward Capriolo
• Created: 22/Jan/17 20:44
• Updated: 10/Mar/17 12:31
• Resolved: 10/Mar/17 12:31

Description

There are a few sources of ugly boiler plate

• to many classes have overloaded constructors
• GossipSettings could use jackson vs DOM parsing
• many classes could use immutable style and less setter/getters
• we have one thing built with a builder but we dont use that pattern everywhere
  *GossipService GossipManager GossipCore GossipRunner, way to many chained calls really confusing and unnessary heirarchy. Should be two classes tops

A good get your feet wet issue is a cleanup of this.