When using a non standard represention strategy (like HexadecimalRepresentation) sizes in ShouldHaveSameSizeAs and ShouldHaveSize error messages were not represented in standard representation but were in the non non standard represention used.
remove date conversion in hexadecimal and binary as it is not relevant (you can't use binary/hexadecimal representation when using date assertions)
Add build status
Cosmetical changes
Merge pull request #168 from mariuszs/topic/cosmetic

Cosmetical changes
rename asHexadecimal -> inHexadecimal, asBinary -> inBinary and asUnicode -> inUnicode
make inUnicode() available for char arrays
Issue #116 fixed
Configure locale EN as @before in test instead of in POM to be able to pass test in Eclipse.
Issue #144 - extracting private fields with possibility to disallow it globally
Should allow to extract private fields #144 : add setAllowExtractingPrivateFields to Assertions to make it easy to find and remove unused code
Resolves #151 - add CharSequence hasSameSizeAs assertion that takes a CharSequence
added javadoc example for CharSequence hasSameSizeAs assertion
minor fixes - boy scout rule
Merge pull request #169 from kamilszymanski/issue151

add CharSequence hasSameSizeAs assertion that takes a CharSequence
Resolves #151 - add CharSequence hasSameSizeAs assertion that takes a CharSequence
Use shouldHaveSameSizeAs error message instead of shouldHaveSize
Fix #159 add org.fest.util dependencies assertj-swing depends on
idea output ignore
Fix some of the Dates.assertIsInThePast unit tests that were not well written and failed on slow computers.
Clearer BDDAssertions javadoc example
add isCloseTo assertion for float, double and BigDecimal