Hi,
I have posted a candidate for the Apache Jackrabbit 1.6.0 release at
http://people.apache.org/~jukka/jackrabbit/1.6.0/
See the RELEASE-NOTES.txt file (also included at the end of this
message) for details on release contents and latest changes. The
release candidate is a jar archive of the sources in
http://svn.apache.org/repos/asf/jackrabbit/tags/1.6.0. The SHA1
checksum of the jackrabbit-1.6.0-src.jar release package is
1d3c0971b4f9ed8687f9e761c7781784f197f29a.
Please vote on releasing this package as Apache Jackrabbit 1.6.0. The
vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[ ] +1 Release this package as Apache Jackrabbit 1.6.0
[ ] -1 Do not release this package because...
With the source release I have also included pre-compiled binaries for
the main deployment packages (webapp, jca, standalone). A staged Maven
repository can be reviewed at
https://repository.apache.org/content/repositories/jackrabbit-019/. If
this vote passes, I'll make the release packages available on the
Jackrabbit download page and push the staged repository out to Maven
central.
Here's my +1.
BR,
Jukka Zitting
Release Notes -- Apache Jackrabbit -- Version 1.6.0
Introduction
------------
Apache Jackrabbit 1.6 is an incremental feature release. While
remaining compatible with previous releases, Jackrabbit 1.6 introduces
a number of new features, improvements and fixes to known issues.
The most notable changes in this release are:
* The RepositoryCopier tool makes it easy to backup and migrate
repositories (JCR-442). There is also improved support for selectively
copying content and version histories between repositories (JCR-1972).
* A new WebDAV-based JCR remoting layer has been added to complement
the existing JCR-RMI layer (JCR-1877, JCR-1958).
* Query performance has been further optimized (JCR-1820, JCR-1855
and JCR-2025).
* Added support for Ingres and MaxDB/SapDB databases (JCR-1960, JCR-1527).
* Session.refresh() can now be used to synchronize a cluster node
with changes from the other nodes in the cluster (JCR-1753).
* Unreferenced version histories are now automatically removed once
all the contained versions have been removed (JCR-134).
* Standalone components like the JCR-RMI layer and the OCM framework
have been moved to a separate JCR Commons subproject of Jackrabbit,
and are not included in this release. Updates to those components
will be distributed as separate releases.
* Development preview: There are even more JSR 283 features in
Jackrabbit 1.6 than were included in the 1.5 version. These new
features are accessible through special "jsr283" interfaces in
the Jackrabbit API. Note that none of these features are ready
for production use, and will be replaced with final JCR 2.0 versions
in Jackrabbit 2.0.
See the Jackrabbit issue tracker for all the 120 changes in this release:
https://issues.apache.org/jira/browse/JCR
The issue tracker also documents all the known issues in this release.
Release Contents
----------------
This release consists of a single source archive (jackrabbit-1.6.0-src.jar)
that contains all the Apache Jackrabbit components. Use the following
commands (or the equivalent in your system) to build the release with
Maven 2 and Java 1.4 or higher:
jar xf jackrabbit-1.6.0-src.jar
cd jackrabbit-1.6.0-src
mvn install
The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
https://svn.apache.org/repos/asf/jackrabbit/dist/KEYS.
Upgrading to Jackrabbit 1.6
---------------------------
Apache Jackrabbit 1.6 is fully compatible with the previous 1.x releases.
A previous Apache Jackrabbit 1.x installation can be upgraded by replacing
the relevant jar files with the new versions and adding some new dependencies.
No changes to repository contents are needed.
The Lucene dependency was upgraded to 2.4.1. Note that Jackrabbit 1.6 only
works with this version of Lucene, not with earlier versions and possibly
not even with later versions due to the tight integration with Lucene
internals (JCR-1855).
The POI dependency was upgraded to 3.2-FINAL.
Repository configuration has been extended with options for the repository
lock mechanism. No changes to existing configuration files are needed unless
you need to use this new feature (JCR-1605).
Contributors
------------
The following people have contributed to this release by submitting bug
reports or by participating in the issue resolution process.
Alessandro Cosenza Dominique Pfister Murray Armfield
Alexander Klimetschek Eric Wout van der Steen Nicolas Toper
Angela Schreiber Fabrizio Giustina Oleg Alexeyev
Ard Schrijvers Felix Meschberger Paco Avila
Arthur Meyer Greg Klebus Roman Puchkovskiy
Attila Király Jacco van Weert Ryan Vanderwerf
Bart van der Schans James Abley Sandrine Raffalli
Boni Gopalan Jason Gritman Savvas Triantafyllou
Brian Whipple Jukka Zitting Sébastien Launay
Cédric Damioli Julian Reschke Stefan Guggisberg
Charles Brooking Julian Sedding Stephane Landelle
Christian Ken Yue Thomas Fromm
Christophe Lombart Marcel Reutegger Thomas Mueller
Claus Köll Marius Ropotica Tobias Bocanegra
Dan Diephouse Martijn Hendriks Torsten Weck
Dave Brosius Micah Whitacre Tyson Norris
Dirk Feufel Michael Dürig Yoav Landman
Thank you to everyone involved!
About Apache Jackrabbit
-----------------------
Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR). A content repository is a
hierarchical content store with support for structured and unstructured
content, full text search, versioning, transactions, observation, and
more. Typical applications that use content repositories include content
management, document management, and records management systems.
For more information, visit http://jackrabbit.apache.org/
About The Apache Software Foundation
------------------------------------
Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 100 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 2,500+ contributors.
For more information, visit http://www.apache.org/