Apache Lucene.Net 3.0.3 - Oct 10, 2012
Use the links below to download the Lucene.Net from one of our mirrors.
Mirror
[if-any logo] [end] The currently selected mirror is [preferred]. If you encounter a problem with this mirror, please select another mirror. If all mirrors are failing, there are backup mirrors (at the end of the mirrors list) that should be available.
You may also consult the complete list of mirrors.- Binary / PGP Signature / SHA1 Checksum / MD5 Checksum
- Source / PGP Signature / SHA1 Checksum / MD5 Checksum
Note: RC2 was the release that we voted to pass - those are the release artifacts
Cutting Edge Source Tree
see also the source code section on the community page.
Release Archives
All old releases can be downloaded from the ASF's distribution archive.
Tags of the Source Tree
Verify the integrity of the files
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases.
The PGP signatures can be verified using PGP or GPG. First download the
KEYS as well as the asc
signature file for the relevant distribution. Make sure you get these files
from the main distribution directory ,
rather than from a mirror. Then verify the signatures using
% pgpk -a KEYS
or
% pgpv Apache-Lucene.Net-3.0.3-RC2.src.zip.asc% pgp -ka KEYS or
% pgp
Apache-Lucene.Net-3.0.3-RC2.src.zip.asc% gpg --import
KEYS
% gpg --verify Apache-Lucene.Net-3.0.3-RC2.src.zip.asc
Alternatively, you can verify the MD5 or SHA1 signature on the files. A unix
program called md5 or md5sum is included in many unix distributions. It
is also available as part of GNU
Textutils. Windows
users can get binary md5 programs from here
, here , or
here. An MD5 signature consists of 32 hex
characters, and a SHA1 signature consists of 40 hex characters. Ensure your
generated signature string matches the signature string published in the
files above.