jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ju...@apache.org
Subject svn commit: r1202822 - /jackrabbit/branches/2.2/RELEASE-NOTES.txt
Date Wed, 16 Nov 2011 18:23:16 GMT
Author: jukka
Date: Wed Nov 16 18:23:15 2011
New Revision: 1202822

URL: http://svn.apache.org/viewvc?rev=1202822&view=rev
Log:
2.2: Update release notes.

Modified:
    jackrabbit/branches/2.2/RELEASE-NOTES.txt

Modified: jackrabbit/branches/2.2/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/jackrabbit/branches/2.2/RELEASE-NOTES.txt?rev=1202822&r1=1202821&r2=1202822&view=diff
==============================================================================
--- jackrabbit/branches/2.2/RELEASE-NOTES.txt (original)
+++ jackrabbit/branches/2.2/RELEASE-NOTES.txt Wed Nov 16 18:23:15 2011
@@ -1,4 +1,4 @@
-Release Notes -- Apache Jackrabbit -- Version 2.2.9
+Release Notes -- Apache Jackrabbit -- Version 2.2.10
 
 Introduction
 ------------
@@ -7,42 +7,61 @@ This is Apache Jackrabbit(TM) 2.2, a ful
 Content Repository for Java(TM) Technology API, version 2.0 (JCR 2.0) as
 specified in the Java Specification Request 283 (JSR 283).
 
-Apache Jackrabbit 2.2.9 is patch release that contains fixes and
+Apache Jackrabbit 2.2.10 is patch release that contains fixes and
 improvements over previous 2.2.x releases. This release is backwards
 compatible with all earlier 2.x releases.
 
-Data consistency issue in 2.2.[0-6]
------------------------------------
-
-Earlier 2.2.x releases (< 2.2.7) had a problem where very large positive
-or negative long property values (more than 62 bits) could not be correctly
-read from the reepository. The values are still correctly stored in the
-reporistory, and can be properly read after upgrading to this release,
-but any previous computations or other information derived from such
-properties should be checked for correctness.
-
 Changes in this release
 -----------------------
 
+Improvements
+
+  [JCR-3085] better diagnostics when version storage is broken
+  [JCR-3098] Add hit miss statistics and logging to caches
+
 Bug fixes
 
-  [JCR-2272] Errors during concurrent session import of nodes with same UUIDs
-  [JCR-2962] InputStream not being explicitly closed
-  [JCR-2967] SessionItemStateManager.getIdOfRootTransientNodeState() ...
-  [JCR-2969] FileDataStore garbage collection can throw a ...
-  [JCR-3052] spi2dav: avoid reusing the same document in repositoryserviceimpl
-  [JCR-3063] NullPointerException in ItemManager
-  [JCR-3065] ConcurrentModificationException in FineGrainedISMLocking
-  [JCR-3075] incorrect HTML excerpt generation for queries on japanese ...
-  [JCR-3077] WeightedHighlighter does not encode XML markup characters
-  [JCR-3063] NullPointerException in ItemManager
-  [JCR-3083] Degrade gracefully when reading invalid date values
+  [JCR-2026] DbDataStore: garbage collection deadlock
+  [JCR-2861] Internal Timeout Handling in the TransactionContext is not ...
+  [JCR-2863] Session#importXML can't handle properly uuid collision if ...
+  [JCR-2883] Node.orderBefore and JackrabbitNode.rename should check for ...
+  [JCR-2892] Large fetch sizes have potentially deleterious effects on ...
+  [JCR-2899] [patch] fix uppercase/lowercase handling for not equal to
+  [JCR-2903] Session.importXml should close the input stream (as to ...
+  [JCR-2920] Workspace.copy(src, dest) throws unexpected ...
+  [JCR-2921] URIResolverImpl: use of bitwise instead of logical AND operator
+  [JCR-2922] JcrParser: use of bitwise instead of logical AND operator
+  [JCR-2954] SQL-2 query returns more than the requested column
+  [JCR-3017] Version history recovery fails in case a version does not ...
+  [JCR-3086] potential infinite loop around InternalVersionImpl.getSuccessors
+  [JCR-3089] javax.jcr.RepositoryException when a JOIN SQL2 query is ...
+  [JCR-3090] setFetchSize() fails in getAllNodeIds()
+  [JCR-3101] recovery tool does not recover when version history can be ...
+  [JCR-3105] NPE when versioning operations are concurrent
+  [JCR-3108] SQL2 ISDESCENDANTNODE can throw BooleanQuery#TooManyClauses ...
+  [JCR-3111] InternalVersionManagerBase; missing null check after getNode()
+  [JCR-3112] NodeTypeDefDiff.PropDefDiff.init() constraints change check bugs
+  [JCR-3115] Versioning fixup leaves persistence in a state where the ...
+  [JCR-3116] Cluster Node ID should be trimmed
+  [JCR-3126] The CredentialsWrapper should use a empty String as userId ...
+  [JCR-3128] Problem with formerly escaped JCR node names when upgrading ...
+  [JCR-3139] missing sync in InternalVersionManagerImpl.externalUpdate ...
 
 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
 
+Data consistency issue in 2.2.[0-6]
+-----------------------------------
+
+Earlier 2.2.x releases (< 2.2.7) had a problem where very large positive
+or negative long property values (more than 62 bits) could not be correctly
+read from the reepository. The values are still correctly stored in the
+reporistory, and can be properly read after upgrading to this release,
+but any previous computations or other information derived from such
+properties should be checked for correctness.
+
 Release Contents
 ----------------
 



Mime
View raw message