v2.0.1

ValidationException now sets the exception message with the stringified violations.

v2.0.0

The way of working for some validation rules has changed.
Previously some of them were performing a notNullRule check before this their own work. This was some not needed since it was breaking the single responsibility principle and was also forcing the client of the API to use extra not null checks in order to apply the rule.
Currently if the value passed to those validation rules is null then the validation is considered as passed and no violation is returned.
The changed rules are: lengthBetween, matchRegexRule, inRangeRule, minRule, positiveOrZeroRule, positiveRule, negativeOrZeroRule, negativeRule, maxRule, compareComparableRule, compareStringsRule.

v1.1.1

• adding validation rules: positive, negative, positiveOrZero, negativeOrZero
• changing equalsToRule message
• adding TestUtils

v1.0.2

• adding ValidationEngine methods which accept Collection as input
• adding ViolationProviderUtils

v1.0.1

• adding isTrue and isFalse validation rules
• fixing typo in compareComparables by renaming them into compareComparable

v1.0.0

fix docs