[jira] [Updated] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4967: Fix Version/s: 21.21.21 (was: 2.21.22) > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 21.21.21 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[ANNOUNCE] Apache Jackrabbit Oak 1.60.0 released
The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.60.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 Oak -- Version 1.60.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.60.0 is an incremental feature release based on and compatible with earlier stable Jackrabbit Oak 1.x releases. This release is considered stable and targeted for production use. While Oak 1.60.0 compiles and tests successfully on Java 17, Javadocs generation fails on Java 17 (but works as expected on Java 11). 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.60.0 - Sub-task [OAK-10488] - Benchmark results [OAK-10522] - o.a.j.o.index.ReindexIT#reindexIgnoreMissingTikaDepThrow() fails with Java 21 Technical task [OAK-6757] - Convert oak-auth-ldap to OSGi R7 annotations [OAK-6760] - Convert oak-blob-cloud to OSGi R7 annotations [OAK-10478] - Update Mockito dependency to 5.x [OAK-10502] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 31.0 [OAK-10507] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 31.1 [OAK-10508] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.0.0 [OAK-10510] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.0.1 [OAK-10512] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.1.0 [OAK-10513] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.1.1 [OAK-10515] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.1.2 [OAK-10516] - oak-segment-azure/oak-blob-cloud-azure: update embedded Guava to 32.1.3 [OAK-10521] - Update Easymock dependency to 5.2 [OAK-10524] - SameNameSiblingTest: add (failing) test for getName() semantics [OAK-10545] - oak-jcr: add test for observing effect of remapping a namespace prefix to a different namespace name Bug [OAK-9459] - ConstraintViolationException in VersionManagerImplRestore when target node has a property definition unknown by the frozen node [OAK-9705] - Explain Query tool doesn't show the correct ES query when suggest queries are made [OAK-10006] - AzurePersistence can still write segments after having lost lease to another instance [OAK-10460] - PIPELINED strategy fails with OOME during final merge phase for very large repositories [OAK-10462] - o.a.j.o.plugins.version.VersionEditor#propertyAdded() may mistakenly assume an ongoing restore operation [OAK-10471] - Implement ConflictHandler for UserPrincipalProvider Cache [OAK-10486] - Resolution of inherited groups may terminate pre-maturely for external users [OAK-10495] - Ignore DocumentStoreIndexerIT#parallelReindex* tests [OAK-10517] - Consistently clean membership when switch between default and dynamic sync [OAK-10525] - DefaultSyncContext.createValues : return value should be annotated with @NotNull [OAK-10526] - split doc can contain still referenced revisions without _sdMaxRevTime indicating so [OAK-10542] - resolution of _deleted value ignores split docs in certain cases [OAK-10547] - Indexing job fails at the end of reindexing if it took more than 24h to run [OAK-10565] - document-store: VersionGarbageCollectorIT does not stop background threads Story [OAK-10311] - Optimize SegmentBlob#equals for segment blobs that originate from the same blob store Improvement [OAK-9796] - oak-segment-remote and oak-segment-aws Redis tests fail with ARM processor (Apple M1) [OAK-9949] - Enable offline tail compaction [OAK-10420] - Tool to compare Lucene index content [OAK-10437] - Deprecate all download strategies except PIPELINED [OAK-10487] - oak-search-elastic should perform a count request for fastQuerySize [OAK-10490] - Suggest queries return duplicate entries if prefetch is enabled [OAK-10491] - Indexing: pass a MongoDatabase instance instead of MongoConnection to indexing logic [OAK-10504] - Add indexing job total duration log message [OAK-10505] - Make PIPELINED the default download strategy in the indexing job [OAK-10511] - Get blobId without additional network roundtrip [OAK-10518] - IndexInfo should have a isActive() method [OAK-10519] - Export metrics from indexing job [OAK-10527] - Improve readability of the explain query output [OAK-10538] - Pipeline strategy: eliminate unnecessary intermediate copy of entries in transform stage [OAK-10541] - Pipelined strategy: improve mem
[jira] [Commented] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793730#comment-17793730 ] Manfred Baedke commented on JCR-4967: - ??Depends on how frequently "isCheckedOut" is needed.?? Yes, obviously. Let me rephrase: Is isCheckedOut actually called that often? :) > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793725#comment-17793725 ] Julian Reschke commented on JCR-4967: - trunk: [r1914385|http://svn.apache.org/r1914385] > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4967. - Resolution: Fixed > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4967: Labels: candidate_jackrabbit_2_20 (was: ) > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_jackrabbit_2_20 > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 in /jackrabbit-parent [jackrabbit]
dependabot[bot] commented on PR #145: URL: https://github.com/apache/jackrabbit/pull/145#issuecomment-1842902125 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jackrabbit.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 in /jackrabbit-parent [jackrabbit]
asfgit closed pull request #145: Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 in /jackrabbit-parent URL: https://github.com/apache/jackrabbit/pull/145 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jackrabbit.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (JCR-5007) Checked-out state of non-versionable nodes is not handled correctly
[ https://issues.apache.org/jira/browse/JCR-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793697#comment-17793697 ] Julian Reschke commented on JCR-5007: - Found: https://github.com/apache/jackrabbit/blob/3b823c7e127b89022d7ce1d054cd5b14747ba2cc/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/NodeImpl.java#L2853-L2855 > Checked-out state of non-versionable nodes is not handled correctly > --- > > Key: JCR-5007 > URL: https://issues.apache.org/jira/browse/JCR-5007 > Project: Jackrabbit Content Repository > Issue Type: Bug > Components: core >Reporter: Julian Reschke >Priority: Major > > The implementation always uses the value of the property jcr:isCheckedOut if > it's present, but it also needs to check if the node is actually versionable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4967: Fix Version/s: 2.22 2.21.22 > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793696#comment-17793696 ] Julian Reschke commented on JCR-4967: - Depends on how frequently "isCheckedOut" is needed. I'll now add the test and mark it as failing (see JCR-5007). > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 2.22, 2.21.22 > > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCR-5007) Checked-out state of non-versionable nodes is not handled correctly
Julian Reschke created JCR-5007: --- Summary: Checked-out state of non-versionable nodes is not handled correctly Key: JCR-5007 URL: https://issues.apache.org/jira/browse/JCR-5007 Project: Jackrabbit Content Repository Issue Type: Bug Components: core Reporter: Julian Reschke The implementation always uses the value of the property jcr:isCheckedOut if it's present, but it also needs to check if the node is actually versionable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793688#comment-17793688 ] Manfred Baedke commented on JCR-4967: - Yes. Is performance actually a concern there? > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JCR-4967) test coverage for modification of non-versioned node with jcr:isCheckedOut==false property
[ https://issues.apache.org/jira/browse/JCR-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793677#comment-17793677 ] Julian Reschke commented on JCR-4967: - Found: https://github.com/apache/jackrabbit/blob/3b823c7e127b89022d7ce1d054cd5b14747ba2cc/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/NodeImpl.java#L2853-L2855 > test coverage for modification of non-versioned node with > jcr:isCheckedOut==false property > -- > > Key: JCR-4967 > URL: https://issues.apache.org/jira/browse/JCR-4967 > Project: Jackrabbit Content Repository > Issue Type: Test > Components: core >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Attachments: JCR-4967.diff > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (JCRVLT-736) Allow to write validation CSV files without breaking the build
Konrad Windszus created JCRVLT-736: -- Summary: Allow to write validation CSV files without breaking the build Key: JCRVLT-736 URL: https://issues.apache.org/jira/browse/JCRVLT-736 Project: Jackrabbit FileVault Issue Type: Improvement Components: package maven plugin Reporter: Konrad Windszus In order to create all validation issues in separate CSV files for a reactor build one needs to tweak the severity of issues currently. It would be beneficial to have an option to not fail the build in case CSV reports are being generated in order to built all reports of all modules in one go. -- This message was sent by Atlassian Jira (v8.20.10#820010)
