using check-release.sh everything seems fine. However, I had a test
failure on the first build:
testCloseSessionWhileRunningGc(org.apache.jackrabbit.core.data.GarbageCollectorTest)
Time elapsed: 0.548 sec <<< FAILURE!
junit.framework.AssertionFailedError: Exception 'session has been
closed' expected
at junit.framework.Assert.fail(Assert.java:47)
at
org.apache.jackrabbit.core.data.GarbageCollectorTest.testCloseSessionWhileRunningGc(GarbageCollectorTest.java:68)
With the second build all tests passed.
So +1 given above failure is not considered a blocker.
Michael
On 31.1.12 10:43, Jukka Zitting wrote:
Hi,
A candidate for the Jackrabbit 2.2.11 release is available at:
http://people.apache.org/~jukka/jackrabbit/2.2.11/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbit/tags/2.2.11/
The SHA1 checksum of the archive is 9d7c16265ee5c8578fef3b120389a0c22a4e4d4f.
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-163/
The command for running automated checks against this release candidate is:
$ sh check-release.sh jukka 2.2.11 9d7c16265ee5c8578fef3b120389a0c22a4e4d4f
Please vote on releasing this package as Apache Jackrabbit 2.2.11.
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 2.2.11
[ ] -1 Do not release this package because...
My vote is +1.
BR,
Jukka Zitting
