| Search Apache POI |
| # Apache POI - Download Release Artifacts ### Available Downloads This page provides instructions on how to download and verify the Apache POI release artifacts. There are different versions available depending on how stable your code should be. The latest beta release is Apache POI 3.17-beta1 The latest stable release is Apache POI 3.16 Nightly/CI builds are available as well Archives of all prior releases Apache POI releases are available under the Apache License, Version 2.0. See the NOTICE file contained in each release artifact for applicable copyright attribution notices. To ensure that you have downloaded the true release you should verify the integrity of the files using the signatures and checksums available from this page. ### 01 July 2017 - POI 3.17-beta1 available The Apache POI team is pleased to announce the release of 3.17-beta1. Featured are a handful of new areas of functionality and numerous bug fixes. A summary of changes is available in the Release Notes. A full list of changes is available in the change log. People interested should also follow the dev list to track progress. The POI source release as well as the pre-built binary deployment packages are listed below. Pre-built versions of all POI components are available in the central Maven repository under Group ID "org.apache.poi" and Version "3.17-beta1". #### Binary Distribution poi-bin-3.17-beta1-20170701.tar.gz (20.11 MB, signature (.asc)) MD5 checksum: b0c29f837c4fe411c76ac73899f6cef3 SHA1 checksum: 5f9a85afa374209d885243051bd25b1f3524df35 poi-bin-3.17-beta1-20170701.zip (28.69 MB, signature (.asc)) MD5 checksum: 01a851625c1e4f07e7c794a9a1ee34df SHA1 checksum: 3c5bc487c842c7f6f65384be3a6f82538103892d #### Source Distribution poi-src-3.17-beta1-20170701.tar.gz (82.73 MB, signature (.asc)) MD5 checksum: e70a44b2fe7abc8770e43fc7a1c37b59 SHA1 checksum: fe9c808d38139fc7efe2de6c0a1a8d41283973cc poi-src-3.17-beta1-20170701.zip (86.87 MB, signature (.asc)) MD5 checksum: 5da06274e9a4ff9f22e1631408d68d5d SHA1 checksum: 89e49927dd598f1a8b63b7febd7db3b5cb8dfa26 ### 19 April 2017 - POI 3.16 available The Apache POI team is pleased to announce the release of 3.16. Featured are a handful of new areas of functionality and numerous bug fixes. A summary of changes is available in the Release Notes. A full list of changes is available in the change log. People interested should also follow the dev list to track progress. The POI source release as well as the pre-built binary deployment packages are listed below. Pre-built versions of all POI components are available in the central Maven repository under Group ID "org.apache.poi" and Version "3.16". #### Binary Distribution poi-bin-3.16-20170419.tar.gz (19.96 MB, signature (.asc)) MD5 checksum: 4993db375f9b49b254ee239f1bc09202 SHA1 checksum: 33a2b41547e43f2dad3d1d13a08a122b422a605a poi-bin-3.16-20170419.zip (28.49 MB, signature (.asc)) MD5 checksum: c0b16803ee4ebdc1da1240c7fb28c997 SHA1 checksum: 43672d02682bf5b88f01f35c5da6cf05b9d9d844 #### Source Distribution poi-src-3.16-20170419.tar.gz (82.00 MB, signature (.asc)) MD5 checksum: 3bed80f7a54218f4da3077008839609a SHA1 checksum: a0b86254ccbea1fe7252b29416faa10ff4ccb865 poi-src-3.16-20170419.zip (86.07 MB, signature (.asc)) MD5 checksum: 775835a993b71912f9c098ed73abdb6d SHA1 checksum: 608ed8d9abffab26fcbebaa33c5b222cef545ea8 ### Nightly Builds The POI nightly builds are run on the Jenkins continuous integration server. These builds should not be used in production: they are mostly intended for use by developers to help with resolving bugs and evaluating new features or users who want to try out the latest version. Last Successful Jenkins build for POI-trunk ### Verify It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases. This page provides detailed instructions which you can use for POI artifacts. The PGP signatures can be verified using PGP or GPG. First download the KEYS file as well as the .asc signature files for the relevant release packages. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures. As an example:
    % pgpk -a KEYS
    % pgpv poi-X.Y.Z.jar.asc
or
    % pgp -ka KEYS
    % pgp poi-X.Y.Z.jar.asc
or
    % gpg --import KEYS
    % gpg --verify poi-X.Y.Z.jar.asc poi-X.Y.Z.jar
Sample verification of poi-bin-3.5-FINAL-20090928.tar.gz
    % gpg --import KEYS
    gpg: key 12DAE9BE: "Glen Stampoultzis <glens at apache dot org>" not changed
    gpg: key 4CEED75F: "Nick Burch <nick at gagravarr dot org>" not changed
    gpg: key 84B5A42E: "Rainer Klute <rainer.klute at gmx dot de>" not changed
    gpg: key F5BB52CD: "Yegor Kozlov <yegor.kozlov at gmail dot com>" not changed
    gpg: Total number processed: 4
    gpg:              unchanged: 4
    % gpg --verify poi-bin-3.5-FINAL-20090928.tar.gz.asc poi-bin-3.5-FINAL-20090928.tar.gz
    gpg: Signature made Mon Sep 28 10:28:25 2009 PDT using DSA key ID F5BB52CD
    gpg: Good signature from "Yegor Kozlov <yegor.kozlov at gmail dot com>"
    gpg:                 aka "Yegor Kozlov <yegor at dinom dot ru>"
    gpg:                 aka "Yegor Kozlov <yegor at apache dot org>"
    Primary key fingerprint: 7D77 0C77 6CE7 754E E6AF  23AA 6934 0A02 F5BB 52CD
    % gpg --fingerprint F5BB52CD
    pub   1024D/F5BB52CD 2007-06-18 [expires: 2012-06-16]
           Key fingerprint = 7D77 0C77 6CE7 754E E6AF  23AA 6934 0A02 F5BB 52CD
    uid                  Yegor Kozlov <yegor.kozlov at gmail dot com>
    uid                  Yegor Kozlov <yegor at dinom dot ru>
    uid                  Yegor Kozlov <yegor at apache dot org>
    sub   4096g/7B45A98A 2007-06-18 [expires: 2012-06-16]
### Release Archives Apache POI became a top level project in June 2007 and POI 3.0 artifacts were re-released. Prior to that date POI was a sub-project of Apache Jakarta. Binary Artifacts Source Artifacts Keys Artifacts from prior to 3.0