[jira] [Resolved] (JCR-4233) Update H2DB test dependency

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4233. - Resolution: Fixed Fix Version/s: 2.17.0 2.18 > Update H2DB test

[jira] [Commented] (JCR-4233) Update H2DB test dependency

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281961#comment-16281961 ] Julian Reschke commented on JCR-4233: - trunk: [r1817377|http://svn.apache.org/r1817377] > Update H2DB

[jira] [Created] (JCR-4233) Update H2DB test dependency

2017-12-07 Thread Julian Reschke (JIRA)
Julian Reschke created JCR-4233: --- Summary: Update H2DB test dependency Key: JCR-4233 URL: https://issues.apache.org/jira/browse/JCR-4233 Project: Jackrabbit Content Repository Issue Type: Task

[jira] [Commented] (JCRVLT-248) Support install hook bundles

2017-12-07 Thread Tobias Bocanegra (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281934#comment-16281934 ] Tobias Bocanegra commented on JCRVLT-248: - [~cziegeler] whis the simplest way to start oak in an

[jira] [Comment Edited] (JCRVLT-248) Support install hook bundles

2017-12-07 Thread Tobias Bocanegra (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281934#comment-16281934 ] Tobias Bocanegra edited comment on JCRVLT-248 at 12/7/17 2:43 PM: --

[jira] [Updated] (JCR-4233) Update H2DB test dependency

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4233: Labels: candidate_jcr_2_16 (was: ) > Update H2DB test dependency > --- > >

[jira] [Updated] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4222: Summary: Document reduced RMI interop with older servers after java-9 related changes (was: Document

[jira] [Resolved] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4222. - Resolution: Fixed Fix Version/s: 2.17.0 > Document reduced RMI interop with older servers

[jira] [Created] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Henry Kuijpers (JIRA)
Henry Kuijpers created JCR-4232: --- Summary: GQL: Unexpected/strange behavior when searching for wildcards on property names Key: JCR-4232 URL: https://issues.apache.org/jira/browse/JCR-4232 Project:

[jira] [Updated] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4232: Issue Type: Wish (was: Bug) > GQL: Unexpected/strange behavior when searching for wildcards on

[jira] [Commented] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281569#comment-16281569 ] Julian Reschke commented on JCR-4222: - trunk: [r1817341|http://svn.apache.org/r1817341] > Document

[jira] [Comment Edited] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281569#comment-16281569 ] Julian Reschke edited comment on JCR-4222 at 12/7/17 9:46 AM: -- trunk:

[jira] [Commented] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281711#comment-16281711 ] Julian Reschke commented on JCR-4232: - FWIW, {noformat} "./name":a {noformat} might circumvent the

Jackrabbit-trunk - Build # 2547 - Still Failing

2017-12-07 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit-trunk (build #2547) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2547/ to view the results.

[jira] [Updated] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Henry Kuijpers (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Kuijpers updated JCR-4232: Description: When using the Bulk Editor feature in AEM, the Jackrabbit GQL integration is actually

[jira] [Updated] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4232: Priority: Major (was: Critical) > GQL: Unexpected/strange behavior when searching for wildcards on

[jira] [Commented] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281705#comment-16281705 ] Julian Reschke commented on JCR-4232: - As far as I can tell, this is actually documented behavior:

[jira] [Resolved] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-4232. --- Resolution: Won't Do As referenced by Julian, this works as documented and designed. > GQL:

Re: [VOTE] Release Apache Jackrabbit 2.10.7

2017-12-07 Thread Robert Munteanu
On Wed, 2017-12-06 at 11:07 +0100, Julian Reschke wrote: > Please vote on releasing this package as Apache Jackrabbit 2.10.7. +1 [INFO] [INFO] Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;

[jira] [Updated] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4222: Labels: (was: candidate_jcr_2_16) > Document reduced RMI interop with older servers after java-9

[jira] [Updated] (JCR-4222) Document reduced RMI interop with older servers after java-9 related changes

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4222: Fix Version/s: 2.16.1 > Document reduced RMI interop with older servers after java-9 related changes

[jira] [Updated] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Henry Kuijpers (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Kuijpers updated JCR-4232: Description: When using the Bulk Editor feature in AEM, the Jackrabbit GQL integration is actually

Re: Oak in Jackrabbit components

2017-12-07 Thread Davide Giannella
On 05/12/2017 12:03, Marcel Reutegger wrote: > I don't have a strong preference, but I would probably only do it in > trunk and only there move the two modules under examples. The > Jackrabbit releases on the maintenance branch would still have the two > modules. It may be a bit strange to

[jira] [Commented] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Henry Kuijpers (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281695#comment-16281695 ] Henry Kuijpers commented on JCR-4232: - [~mreutegg] WDYT? Do you have any suggestions on how to improve

[jira] [Commented] (JCR-4232) GQL: Unexpected/strange behavior when searching for wildcards on property names

2017-12-07 Thread Marcel Reutegger (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281735#comment-16281735 ] Marcel Reutegger commented on JCR-4232: --- Please use the standard JCR query API if you need more

[jira] [Commented] (JCR-4078) occasional test failure in GarbageCollectorTest.testSimultaneousRunGC

2017-12-07 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281889#comment-16281889 ] Julian Reschke commented on JCR-4078: - Test excluded for now with

[jira] [Created] (JCRVLT-251) Child nodes being mentioned in parent node's docview xml is not being cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
Konrad Windszus created JCRVLT-251: -- Summary: Child nodes being mentioned in parent node's docview xml is not being cleared correctly during installation Key: JCRVLT-251 URL:

[jira] [Commented] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282209#comment-16282209 ] Konrad Windszus commented on JCRVLT-251: There is a test case for that in

[jira] [Updated] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-251: --- Summary: Child nodes mentioned in parent node's docview xml are not cleared correctly during

Jackrabbit-trunk - Build # 2548 - Still Failing

2017-12-07 Thread Apache Jenkins Server
The Apache Jenkins build system has built Jackrabbit-trunk (build #2548) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2548/ to view the results.

[jira] [Updated] (JCRVLT-251) Child nodes being mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-251: --- Summary: Child nodes being mentioned in parent node's docview xml are not cleared correctly

[jira] [Comment Edited] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282209#comment-16282209 ] Konrad Windszus edited comment on JCRVLT-251 at 12/7/17 6:01 PM: - There is

[jira] [Commented] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282214#comment-16282214 ] Konrad Windszus commented on JCRVLT-251: It is not 100% clear what is supposed to be expected with

[jira] [Comment Edited] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282214#comment-16282214 ] Konrad Windszus edited comment on JCRVLT-251 at 12/7/17 5:46 PM: - It is

[jira] [Commented] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282224#comment-16282224 ] Konrad Windszus commented on JCRVLT-251: After reading

[jira] [Created] (JCRVLT-250) Test class "SimpleFileAggregateInPackage" not executed by default in maven-surefire-plugin

2017-12-07 Thread Konrad Windszus (JIRA)
Konrad Windszus created JCRVLT-250: -- Summary: Test class "SimpleFileAggregateInPackage" not executed by default in maven-surefire-plugin Key: JCRVLT-250 URL: https://issues.apache.org/jira/browse/JCRVLT-250

[jira] [Updated] (JCRVLT-251) Child nodes mentioned in parent node's docview xml are not cleared correctly during installation

2017-12-07 Thread Konrad Windszus (JIRA)
[ https://issues.apache.org/jira/browse/JCRVLT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated JCRVLT-251: --- Description: If a repository contains the following structure {code} + testroot

Re: Experimental build for Oak on Windows

2017-12-07 Thread Tommaso Teofili
+1 thanks Robert, I had the same experience Michael had a while back. Also to me it looked like many test failures were false negatives, but it may well be that some tests fail reliably on Windows and I didn't notice that. Regards, Tommaso Il giorno gio 7 dic 2017 alle ore 09:11 Michael Dürig

Re: Experimental build for Oak on Windows

2017-12-07 Thread Michael Dürig
Thanks Robert for taking this up again. Almost exactly a year ago I spent some time in understanding Jenkins issues [1]. This showed that back then infrastructure problems prevailed by large. Only a few issues reported by Jenkins were actual regressions. I would be interested to see whether

Re: Experimental build for Oak on Windows

2017-12-07 Thread Julian Reschke
On 2017-12-07 14:21, Tommaso Teofili wrote: +1 thanks Robert, I had the same experience Michael had a while back. Also to me it looked like many test failures were false negatives, but it may well be that some tests fail reliably on Windows and I didn't notice that. Regards, Tommaso If tests