Re: Queries related to Oak

Hi Soumya, Welcome to the list. This is the right place to ask questions. Best regards Michael From: "Banerjee, Soumya J" Reply-To: "oak-dev@jackrabbit.apache.org" Date: Thursday 3 September 2015 08:01 To:

Queries related to Oak

Hi, My team in Tesco, is currently working on developing a platform that uses Jackrabbit Oak as a repository. We are facing a few problems with Oak and have a few queries as well. Also, we are doing a few things in Oak that we are not very sure about (if it is the right way to do it). Can we

Analyze the usages of AbstractServiceTracker

I analyzed some usages of AbstractServiceTracker and I posted my findings in OAK-3346. In my opinion some usages are unjustified, and some are just wrong. Can you please have a look at it?

Re: oak-run upgrade improvements

On Wed, 2015-09-02 at 18:35 +, Tomek Rekawek wrote: > Hi, > > One more thing. The “upgrade" command requires a lot of Maven > dependencies (Amazon API client for the S3 support, Jackrabbit 2 for > the repository upgrades, etc.) Some of these dependencies conflicts > with the Oak modules (eg.

Re: oak-run upgrade improvements

On Thu, 2015-09-03 at 09:59 +0200, Julian Reschke wrote: > On 2015-09-03 09:14, Robert Munteanu wrote: > > On Wed, 2015-09-02 at 18:35 +, Tomek Rekawek wrote: > > > Hi, > > > > > > One more thing. The “upgrade" command requires a lot of Maven > > > dependencies (Amazon API client for the S3

Re: oak-run - quo vadis? (was: oak-run upgrade improvements)

2015-09-03 9:31 GMT+02:00 Julian Sedding : > Hi Tomek > > I believe that benchmarks in oak-run also use Jackrabbit 2 (via fixtures). > However, OAK-3342 proposes moving the benchmarks into their own module. > > Looking at this from a less technical perspective, I propose to

Re: oak-run upgrade improvements

On 2015-09-03 09:14, Robert Munteanu wrote: On Wed, 2015-09-02 at 18:35 +, Tomek Rekawek wrote: Hi, One more thing. The “upgrade" command requires a lot of Maven dependencies (Amazon API client for the S3 support, Jackrabbit 2 for the repository upgrades, etc.) Some of these dependencies

Re: oak-run upgrade improvements

On Thu, Sep 3, 2015 at 10:01 AM, Robert Munteanu wrote: > ... _If_ we decide OSGi, it must be embedded and controlled by the oak > -run instance, and not a general-use OSGi application like e.g. Karaf > with some bundles added... Note that Sling's slingstart-maven-plugin

oak-run - quo vadis? (was: oak-run upgrade improvements)

Hi Tomek I believe that benchmarks in oak-run also use Jackrabbit 2 (via fixtures). However, OAK-3342 proposes moving the benchmarks into their own module. Looking at this from a less technical perspective, I propose to split oak-run into three modules: - oak-dev-tools (benchmarks, scalability,

Re: oak-run - quo vadis? (was: oak-run upgrade improvements)

Hi Julian, Thanks for making this more general. On 03/09/15 09:31, "Julian Sedding" wrote: >(…) split oak-run into three modules: > >- oak-dev-tools >- oak-upgrade >- oak-ops-tool I think it makes perfect sense. Regarding the oak-upgrade, we already have such a

code cleanup vs backports

Hi there, I recently had to backport stuff, and it turned out to be harder than it should have been. This was caused by code cleanup changes that weren't backported and thus caused merge conflicts. Now code cleanup is a good thing, and it needs to be done, for performance, robustness,

Re: oak-run - quo vadis? (was: oak-run upgrade improvements)

Hi Tomek Ideally we can have the NodeStore and DataStore/BlobStore creation in a shared CLI module. That would allow best re-use IMHO. I know that Oak has a flat module structure. Still I would think that putting these split modules + something like "oak-tools-commons" into a folder called

Re: oak-run - quo vadis? (was: oak-run upgrade improvements)

On 03/09/2015 09:31, Julian Sedding wrote: > Hi Tomek > > I believe that benchmarks in oak-run also use Jackrabbit 2 (via fixtures). > However, OAK-3342 proposes moving the benchmarks into their own module. > > Looking at this from a less technical perspective, I propose to split > oak-run into

[Oak origin/1.0] Apache Jackrabbit Oak matrix - Build # 391 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #391) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/391/ to view the results. Changes: [chetanm] OAK-1752 - Node name queries should use an index