Fixing false assumption in TuneCassandra. Previously, there was logic to guard
against yaml config settings that had been added or removed from different versions. This was tested
by adding a null check to see if the setting existed in the yaml that was read in. Unfortunately,
if a property was commented out in the yaml (yet still compltetly valid as a setting) the entry would
not be present in the map that snakeyaml produced, and hence you could never write out that setting.
Basically this was a poor man's way to avoid branching. Now that we branch in priam, that is no longer necessary.
Merge pull request #166 from sagarl/1.1

Filtering/ignoring Dummy nodes as seeds
Merge remote-tracking branch 'upstream/1.1' into 1.1
ffs, the version number again.
why can't this build system get out of the way?
Merge pull request #169 from jasobrown/1.1

ffs, the version number again
Merging dse work into mainline 1.1 branch
reverted the group names back to the correct value
Merge pull request #172 from jasobrown/1.1

merging in changes to allow support of Datastax Enterprise
missing an @Inject annotation - d'oh!
version number
Merge pull request #173 from jasobrown/1.1

missing an @Inject annotation - d'oh!
broken version number, again ... sigh
Merge pull request #174 from jasobrown/1.1

broken version number, again ... sigh
Adding changes to Incremental Restores which will be used during Cluster Migration
Merging changes from 1.1 branch