bval-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Bean Validation > Downloads
Date Fri, 11 Jun 2010 19:28:00 GMT
Space: Apache Bean Validation (
Page: Downloads (

Added by Donald Woods:

Apache Bean Validation provides an implementation of the [Bean Validation Specification (JSR303)|],
which is TCK compliant and works on Java SE 5 or later.

Apache Bean Validation artifacts are distributed in source and binary form under the terms
of the [Apache License, Version 2.0|].  See the
included LICENSE and NOTICE files included in each artifact for additional license information.
 Please read the [Verifying Releases|#Verifying Releases] section below on how to verify the
integrity of downloaded files.

Apache Bean Validation is an effort undergoing [incubation|] at
The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates that the infrastructure,
communications, and decision making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be fully endorsed by
the ASF.


h3. Apache Bean Validation 0.1-incubating - Released June 11, 2010

|| Module || Artifact || Comments ||
| Source | [|]
| Apache Bean Validation source |
| Implementation | [bval-jsr303-0.1-incubating.jar|]
| Apache Bean Validation provider |
| Implementation Bundle | [org.apache.bval.bundle-0.1-incubating.jar|]
| Apache Bean Validation provider w/ OSGi metadata |
| Implementation JavaDoc | [bval-jsr303-0.1-incubating-javadoc.jar|]
| Apache Bean Validation provider JavaDocs |


h3. Maven Users

Our artifacts are published to the Maven Central repository and can be found under:

You'll need to add the following dependencies in your builds (and Maven will automatically
include the additional transitive dependencies for you) -


h3. Verifying Releases

It is essential that you verify the integrity of any downloaded files using the PGP or MD5
signatures.  For more information on signing artifacts and why we do it, checkout the [Release
Signing FAQ|].

The PGP signatures can be verified using PGP or GPG.  First download the [KEYS|]
as well as the asc signature file for the artifact.  Make sure you get these files from the
[main distribution directory|], rather than from
a [mirror|].  Then verify the signatures
$ pgpk -a KEYS
$ pgpv
$ pgp -ka KEYS
$ pgp
$ gpg --import KEYS
$ gpg --verify

Alternatively, you can verify the MD5 signature on the files. A Unix/Linux program called
*md5* or *md5sum* is included in most distributions.  It is also available as part of [GNU
Textutils|]. Windows users can get binary
md5 programs from such places as [here|], [here|],
or [here|]. 

Change your notification preferences:

View raw message