upgrade vijava to latest to solve the following bug:
Vim 3.0 through 7.x before 7.2.010 does not properly escape characters, which allows user-assisted attackers to (1) execute arbitrary shell commands by entering a K keystroke on a line that contains a ";" (semicolon) followed by a command, or execute arbitrary Ex commands by entering an argument after a (2) "Ctrl-]" (control close-square-bracket) or (3) "g]" (g close-square-bracket) keystroke sequence, a different issue than CVE-2008-2712.
The suspicion is that the combination of the latest Java 7 patch doesn’t play along with the old gradle-cobertura plugin (it works fine with Java 6). Updating cobertura to a newer version fixes the build issues.
Making the code more resilient: if the configuration is messed up (empty string or spaces) or simply doesn’t exist, return the default value (and log the error)
Upgrade gradle to 1.12
Fixed cobertura reports
Merge pull request #134 from radonsky/fix_cobertura

Fixed cobertura reports
Merge branch 'fix_cobertura'

* fix_cobertura:
  Fixed cobertura reports
Merge pull request #133 from radonsky/master

Upgrade gradle to 1.12
Merge pull request #135 from Netflix/fix-maxKills-chaos-bug

maxTerminationsPerDay was checked only once for the group before the ite...
maxTerminationsPerDay was checked only once for the group before the iteration over the instances while ee should check if maxTerminationsPerDay was exceeded before trying to terminate *any* instance.
The original condition should be returned in addition to the new one since unit-test will otherwise fail:
the reason for that is that the unit-test checks two things:
1. selected instances
2. terminated

and no instance should be selected if we reached the max.
Though the previous fix ensures that we won’t kill the chosen instance - according to the unit-test we should not even choose it (strict approach).
Merge pull request #136 from Netflix/fix-maxKills-chaos-bug

The original condition should be returned in addition to the new one sin...