Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 8594 invoked from network); 15 Dec 2010 18:33:19 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Dec 2010 18:33:19 -0000 Received: (qmail 5062 invoked by uid 500); 15 Dec 2010 18:33:18 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 4762 invoked by uid 500); 15 Dec 2010 18:33:17 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 4728 invoked by uid 99); 15 Dec 2010 18:33:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 18:33:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com designates 209.85.214.179 as permitted sender) Received: from [209.85.214.179] (HELO mail-iw0-f179.google.com) (209.85.214.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 18:33:08 +0000 Received: by iwn42 with SMTP id 42so2646553iwn.24 for ; Wed, 15 Dec 2010 10:32:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=p3nXP+RC7e2E7zCrXJ2d2FnHJjeJA3WAzFhFSXXgxig=; b=l3EPOh7X5HJwgfE4v/kILoksFKz3dVpd6zPVp+a3ESVgFEvF459qocz79CpeZoZ0Mn qZV7m2acRKRip8kHC4jQS4qvs7V12Ecr7Lj4UPBkAtjwX2zlai39KgJOkHQGLr2s0yTY 9j6+tfJ4lC+9zoV8LQhCTqjwAQz7Vg+KpEsHY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; b=Kx7T9bGvY+eOOaUNidpJloaY0O2MqrqJg6MgYEuKXy/2DJ78QkPivRC42eOSAdrOJ9 KJjYEGRMDHAEyVdV2tldQqtnfmHzeikATS+L3llPbpmHJPym/JJbzBIpEh+VTrjZDQ33 3bckmFH8g8G222nt2vOu4e7ZliVcpJEowHDwY= Received: by 10.231.11.68 with SMTP id s4mr5258035ibs.14.1292437965835; Wed, 15 Dec 2010 10:32:45 -0800 (PST) MIME-Version: 1.0 Sender: jukka.zitting@gmail.com Received: by 10.231.12.7 with HTTP; Wed, 15 Dec 2010 10:32:22 -0800 (PST) From: Jukka Zitting Date: Wed, 15 Dec 2010 20:32:22 +0200 X-Google-Sender-Auth: j291oO3VqWrqvDuo9jgZRF0MGPg Message-ID: Subject: [ANNOUNCE] Apache Jackrabbit 2.2.0 released To: announce@apache.org, announce@jackrabbit.apache.org, Jackrabbit Users , Jackrabbit Developers Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit 2.2.0. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release. Release Notes -- Apache Jackrabbit -- Version 2.2.0 Introduction ------------ This is Apache Jackrabbit(TM) 2.2, a fully compliant implementation of the Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as specified in the Java Specification Request 283 (JSR 283). Changes in this release ----------------------- Jackrabbit 2.2 is an incremental feature release based on the earlier 2.x releases. The most notable changes in this release are: * Performance improvements. The performance of features like access control, user and group management, concurrent read/write operations and join queries have been notably improved. A performance test suite was added to track improvements and prevent regressions. * Deprecation of old persistence managers. All non-bundle persistence managers and also non-pooled bundle database persistence managers have been deprecated in preparation for potential future changes of the persistence layer. All the deprecated persistence managers will remain functional and supported in future 2.x releases, but will most likely be removed in Jackrabbit 3.0. * Better thread-safety. Significant effort has been spent on making Jackrabbit more resilient against various kinds of concurrency issues. Most notably Jackrabbit no longer assumes that clients will follow the JCR specification in not using a single session concurrently from multiple threads. Doing so is still not recommended, but it's no longer likely to cause significant trouble. * Switch from log4j to Logback. The default Jackrabbit deployment packages (jar, war, rar) now use Logback instead of log4j for improved logging functionality. Thanks to the SLF4J logging framework it is still easy for downstream deployments to switch to another logging backend for example if support for existing configurations is needed. * Over 150 other fixes and improvements. For more detailed information about all the changes in this and other Jackrabbit releases, please see the Jackrabbit issue tracker at https://issues.apache.org/jira/browse/JCR Release Contents ---------------- This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.txt file for instructions on how to build this release. 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. 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. 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/