| Release Notes -- Apache Jackrabbit Core -- Version 1.4.8 |
| |
| Introduction |
| ------------ |
| |
| This is the 1.4.8 patch release of the jackrabbit-core component of |
| Apache Jackrabbit, a fully conforming implementation of the Content |
| Repository for Java Technology API (JCR). |
| |
| This release fixes a number of issues. See below for the full list of |
| changes in this release. |
| |
| See the Apache Jackrabbit website at http://jackrabbit.apache.org/ for |
| more information. |
| |
| Changes in this release |
| ----------------------- |
| |
| All the changes in this release are listed below. The issue identifier and |
| title is listed for each change and known issue. You can look up individual |
| issues for more details in the Jackrabbit issue tracker at |
| http://issues.apache.org/jira/browse/JCR |
| |
| Bug fixes |
| [JCR-1572] DbDataStore connection does not always reconnect |
| [JCR-1841] Workspace.xml can't be loaded if it has a BOM |
| [JCR-1866] Query may throw ArrayIndexOutOfBoundsException |
| [JCR-1918] DbDataStore keeps ResultSets open |
| |
| Release Contents |
| ---------------- |
| |
| Like the previous jackrabbit-core 1.4.x releases this patch release only |
| contains the jackrabbit-core component. The component is distributed both |
| as a source archive and a pre-compiled binary. |
| |
| * Source archive (jackrabbit-core-1.4.8-src.jar) |
| |
| The source archive contains the full source code of this release |
| in a "jackrabbit-core-1.4.8" directory. Use the following commands |
| (or the equivalent in your environment) to build the component |
| with Maven 2 and Java 1.4 or higher: |
| |
| $ jar xf jackrabbit-core-1.4.8-src.jar |
| $ cd jackrabbit-core-1.4.8 |
| $ mvn install |
| |
| * Pre-compiled binary (jackrabbit-core-1.4.8.jar) |
| |
| Core of the Apache Jackrabbit content repository implementation. |
| |
| See the included README.txt file for more information. |
| |
| Each release file is accompanied by SHA1 and MD5 checksums and a PGP |
| signature. The public key used for the signatures can be found |
| in the KEYS file. |
| |
| |