Re: Oak Session save behavior

> Now the problem we are running into is, after save operation is performed, > there is no good way for us to know if save was done (Since save in oak is > async). So after save we refresh the page, the user sees old content. Saves in Oak are not async. On a single cluster node if session S1

Commit history missing for files moved to new modules in git-svn/github

Looks like with svn move/copy the history in git is coming out to be blank [2]. In svn it looks fine though [1]. Would it be possible to get git history back (via some other tooling anyone aware of) as it greatly helps in understanding code evolution while analyzing any issue quickly. Otherwise

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.8

> [X] +1 Release this package as Apache Jackrabbit Oak 1.7.8 Thanks, Vikas

Oak Session save behavior

Hello, We are working on a small CMS using Oak-Core (Version 1.6.0) with Play framework and RDBMS as datastore. "mysqlConnectorJava": "mysql:mysql-connector-java:5.1.38", > "oak-jcr": "org.apache.jackrabbit:oak-jcr:1.6.0", > > We use the following code for session handle, public

[jira] [Commented] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

[ https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180926#comment-16180926 ] Peter Yuan commented on JCR-4183: - [~julian.resc...@gmx.de]: Thank you, I've verified it. It's working fine

[jira] [Closed] (JCR-4183) Jackrabbit standalone jar isn't working under Windows 10 and JDK 8

[ https://issues.apache.org/jira/browse/JCR-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Yuan closed JCR-4183. --- I've verified it. It's working fine on the latest build (r1808754). > Jackrabbit standalone jar isn't working

Re: [VOTE] Release Apache Jackrabbit 2.8.6

+1 Release this package as Apache Jackrabbit 2.8.6 D.

Re: Access to NodeStore instance within benchmark

Its bit buried in layers. I saw few other benchmark use reflection to access the NodeStore. So for now using that to move forward Chetan Mehrotra On Tue, Sep 26, 2017 at 3:32 PM, Michael Dürig wrote: > > I tend to agree with Davide. Especially since the use case is for >

Re: Access to NodeStore instance within benchmark

I tend to agree with Davide. Especially since the use case is for benchmarking only. Isn't there an alternative way where the node store could be exposed via the the benchmark's fixture? Michael On 25.09.17 11:00, Davide Giannella wrote: On 25/09/2017 07:05, Chetan Mehrotra wrote: One way

[jira] [Commented] (JCR-3929) Can not create new repository

[ https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180469#comment-16180469 ] Leonidas Beis commented on JCR-3929: I dont think issue 3665 pertains to this, as OP does, we too have a

Re: [VOTE] Release Apache Jackrabbit Oak 1.7.8

[X] +1 Release this package as Apache Jackrabbit Oak 1.7.8 Regards, Andrei 2017-09-25 23:15 GMT+03:00 Davide Giannella : > Please vote on releasing this package as Apache Jackrabbit Oak 1.7.8. > The vote is open for the next 72 hours and passes if a majority of at > least

[jira] [Commented] (JCR-3929) Can not create new repository

[ https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180364#comment-16180364 ] Julian Reschke commented on JCR-3929: - FWIW, the tests create new repositories all the time, so there

[jira] [Commented] (JCR-3929) Can not create new repository

[ https://issues.apache.org/jira/browse/JCR-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180345#comment-16180345 ] Leonidas Beis commented on JCR-3929: +1 for this also. Was using 2.12.1 and had this issue when