Jackrabbit-trunk - Build # 2490 - Unstable

[Apache Jenkins Server]

The Apache Jenkins build system has built Jackrabbit-trunk (build #2490)

Status: Unstable

Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2490/ to 
view the results.

[jira] [Created] (JCR-4137) Release Jackrabbit 2.15.3

[Julian Reschke (JIRA)]

Julian Reschke created JCR-4137:
---

 Summary: Release Jackrabbit 2.15.3
 Key: JCR-4137
 URL: https://issues.apache.org/jira/browse/JCR-4137
 Project: Jackrabbit Content Repository
  Issue Type: Task
Reporter: Julian Reschke
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke resolved JCR-3901.
-
Resolution: Fixed

> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token 
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16, 2.15.3
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

[Julian Reschke (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030691#comment-16030691
 ] 

Julian Reschke commented on JCR-3901:
-

trunk: [r1796980|http://svn.apache.org/r1796980]


> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token 
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16, 2.15.3
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-3901:

Fix Version/s: 2.15.3

> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token 
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16, 2.15.3
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-3901:

Labels: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_14 
candidate_jcr_2_8  (was: )

> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token 
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>  Labels: candidate_jcr_2_10, candidate_jcr_2_12, 
> candidate_jcr_2_14, candidate_jcr_2_8
> Fix For: 2.16
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token transfers

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-3901:

Summary: TCK LockManagerTest does not allow new JCR 2.0 functionality for 
lock token transfers  (was: TCK LockManagerTest does not allow new JCR 2.0 for 
lock token transfers)

> TCK LockManagerTest does not allow new JCR 2.0 functionality for lock token 
> transfers
> -
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

[Julian Reschke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated JCR-3901:

Fix Version/s: 2.16

> TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers
> ---
>
> Key: JCR-3901
> URL: https://issues.apache.org/jira/browse/JCR-3901
> Project: Jackrabbit Content Repository
>  Issue Type: Bug
>  Components: test
>Affects Versions: 2.10.1, 2.8.1, 2.11.0
>Reporter: Julian Reschke
>Assignee: Julian Reschke
> Fix For: 2.16
>
>
> testLockTransfer2() and testAddLockTokenToAnotherSession() assume that it's 
> always illegal to add lock tokens to multiple sessions, however 
>  allows 
> simultaneous lock ownership for open scoped locks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Jackrabbit 2.14.1

[Chetan Mehrotra]

+1
Chetan Mehrotra


On Tue, May 30, 2017 at 2:21 PM, KÖLL Claus  wrote:
> +1
>
> greets
> claus

AW: [VOTE] Release Apache Jackrabbit 2.14.1

[KÖLL Claus]

+1

greets
claus

[ANNOUNCE] Apache Jackrabbit Oak 1.7.0 released

[Davide Giannella]

The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. 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 Oak -- Version 1.7.0

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.7.0 is an unstable release cut directly from
Jackrabbit Oak trunk, with a focus on new features and other
improvements. For production use we recommend the latest stable 1.6.x
release.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.7.0
-

Sub-task

[OAK-5869] - Annotate documents with branch commits
[OAK-5964] - Invalidate documents through journal
[OAK-5968] - Introduce RevisionContext.getClock()

Technical task

[OAK-3690] - Decouple SegmentBufferWriter from SegmentStore
[OAK-5554] - RDB*Store: update postgresql JDBC driver reference to
9.4.1212
[OAK-] - RDB*Store: update Tomcat JDBC pool dependency to
7.0.73
[OAK-5627] - RDBDocumentStore: improve long query logging
[OAK-5652] - RDB*Store: update Oracle JDBC driver reference to
12.1.0.2.0
[OAK-5653] - RDB*Store: update Derby to release 10.13
[OAK-5667] - RDBDocumentStore: remove support for DBs without
support for CASE statements in SELECT
[OAK-5751] - RDBDocumentStore: properly handle null values for
system properties
[OAK-5852] - RDB*Store: update Tomcat JDBC pool dependency to
7.0.75
[OAK-5855] - RDBDocumentStore: improve query support for VersionGC
[OAK-5977] - Document enhancements in S3DataStore in 1.6
[OAK-5981] - SegmentTar version check with disabled mmaping
[OAK-6083] - RDBDocumentStore: implement support for
VersionGCSupport extensions added for OAK-4780
[OAK-6134] - RDB*Store: update PostgreSQL JDBC
[OAK-6140] - Create RDB-specific BlobReferenceIterator
[OAK-6143] - RDB*store fixtures: shorten table name prefixes for
Oracle
[OAK-6176] - Service to provide access to async indexer state
[OAK-6192] - Lucene IndexInfoProvider implementation
[OAK-6207] - RDBDocumentStore: allow schema evolution part 2:
record schema version when updating/inserting rows
[OAK-6216] - Property IndexInfoProvider implementation
[OAK-6224] - Enable dumping index definitions and stats via
oak-run
[OAK-6226] - RDBDocumentStoreDB: missing @Override statements
[OAK-6228] - Enable index consistency check via oak-run
[OAK-6231] - Enable dumping index content via oak-run
[OAK-6236] - Improve the help output from oak-run commands
[OAK-6244] - RDB*Store: update postgresql JDBC driver reference to
42.1.1
[OAK-6247] - RDB*Store: update Tomcat JDBC pool dependency to
7.0.78

Bug

[OAK-4390] - DocumentStoreStatsIT.update fails when RDB's append
mode is disabled
[OAK-4529] - DocumentNodeStore does not have a repository software
version range check
[OAK-5301] - Possible null dereference in MapRecord
[OAK-5355] - Too eager refreshing of tree permissions in
SecureNodeBuilder
[OAK-5357] - StringUtils conversion functions can throw
NullPointerException
[OAK-5441] - Test failure: BasicServerTest.testServerOk() Address
already in use
[OAK-5450] - Documented example for relativeNode in index
aggregation does not work.
[OAK-5500] - Oak Standalone throws ClassNotFoundException:
remoting/protectedHandlersConfig.xml
[OAK-5501] - Oak Standalone: Webdav configuration is set to
remoting mode by default
[OAK-5536] - Facets on relative properties do not work properly
[OAK-5557] - incomplete diffManyChildren during commitHook
evaluation in a persisted branch
[OAK-5573] -
org.apache.jackrabbit.oak.segment.standby.StandbyTestIT.testSyncLoop
[OAK-5580] - Show statistics about I/O operations in the check
command
[OAK-5590] - The check command doesn't do any check when "deep"
option is not provided
[OAK-5601] - documentMk backgroundRead should handle missing
journal entries
[OAK-5619] - withIncludeAncestorsRemove reports unrelated
top-level node deletion
[OAK-5626] - ChangeProcessor doesn't reset 'blocking' flag when
items from queue gets removed and commit-rate-limiter is null
[OAK-5636] - potential NPE in ReplicaSetInfo
[OAK-5649] - Error in RefreshPolicy can lead to IndexNode lock
leak
[OAK-5651] - java.lang.IllegalStateException logged when migrating
Segment to Document
[OAK-5657] - leverage project.version in oak-examples
[OAK-5668] - Test failure:
observation.ObservationQueueFullWarnTest.warnOnRepeatedQueueFull
[OAK-57

Re: [VOTE] Release Apache Jackrabbit 2.14.1

[Tomek Rękawek]

Hi Julian,

> On 29 May 2017, at 11:37, Julian Reschke  wrote:
>[ ] +1 Release this package as Apache Jackrabbit 2.14.1


+1

Regards,
Tomek

-- 
Tomek Rękawek | Adobe Research | www.adobe.com
reka...@adobe.com



smime.p7s
Description: S/MIME cryptographic signature