[jira] [Updated] (GOSSIP-46) Boilder Plate cleanup

["Edward Capriolo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOSSIP-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward Capriolo updated GOSSIP-46:
----------------------------------
    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. 

  was:
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

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


> Boilder Plate cleanup
> ---------------------
>
>                 Key: GOSSIP-46
>                 URL: https://issues.apache.org/jira/browse/GOSSIP-46
>             Project: Gossip
>          Issue Type: Improvement
>            Reporter: Edward Capriolo
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)