Parameters as target

This release only includes a single change: all annotation can now also be applied to method and constructor parameters:

public class Book {
    private String isbn
	
    public Book(@ISBN String isbn) {
        this.isbn = isbn;
    }
} 

In order for this to work you need a framework that takes care of injecting the required validation code for you.

Thanks to @mehranroodsaz for raising this. See #26, #27.

Strong checksums

The only change in this release is that now sha256 and sha512 checksums are published to Maven Central alongside the insecure md5 and sha1 checksums.

Gradle Build

Changes

• Project is now build with Gradle, see #8
• Test fixtures are now published as a separate artifact with GAV com.github.britter:bean-validators:0.7.0:test-fixtures. Please refer to the documentation for more information on how to use test fixtures.

bean-validators v0.6.3

Changes:

• Fix validation for null and blank values in @Alphanumeric & @Alphabetic. Thanks to @tbinias. See #6.
• Updated Apache Commons Lang dependency from 3.5 to 3.6

bean-validators v0.6.2

Changes

• Updated dependencies org.apache.commons:commons-lang3 from 3.4 to 3.5 and commons-validator:commons-validator from 1.5.0 to 1.6. Thanks to @CodingFabian. See #5.
• Fixed some typos in JavaDocs

bean-validator v0.6.1

Changes

• Made all method parameters final where possible
• Added package-info.java files to all packages
• Added JavaDoc to all constraint annotations and validators in the file package

bean-validator v0.6.0

New Features

• All annotations from the file package can now also be applied to Strings. The validators will the create a new File instance using the new File(String) constructor and use that instance for validation.

bean-validator v0.5.1

This release only cleans up dependencies which have been defined in the wrong scope.

Changes

• com.google.guava:guava:18.0 moved from compile scope to test scope
• org.hamcrest:hamcrest-all:1.3 moved from compile scope to test scope

bean-validator v0.5.0

Starting with this release bean-validators uses semantic versioning.

New Features

The file package adds a variety of new constraints for validating java.io.File objects:

• @Directoryand @NotDirectory
• @Existingand @NotExsting
• @Readableand @NotReadable
• ... and a lot more

bean-validators v0.4

New Features

• @ASCII makes sure a String only contains ASCII printable characters (all characters have to be in the range 32 thru 126)
• @JavaNumber makes sure a String contains a valid Java number