[jira] [Comment Edited] (JCRVLT-32) Store package properties in the MANIFEST.MF for faster access

[ https://issues.apache.org/jira/browse/JCRVLT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15960651#comment-15960651 ] Tobias Bocanegra edited comment on JCRVLT-32 at 4/21/17 1:18 AM: - In

[jira] [Comment Edited] (JCRVLT-32) Store package properties in the MANIFEST.MF for faster access

[ https://issues.apache.org/jira/browse/JCRVLT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766247#comment-15766247 ] Tobias Bocanegra edited comment on JCRVLT-32 at 4/21/17 1:17 AM: - suggest

Re: A federated data store

I misremembered above when I was describing a possible implementation. I was thinking we'd add a method to the delegate, but that would be added to the DataStore interface, obviously (not BlobStore or GarbageCollectibleBlobStore). Likewise, the default implementation would exist in

A federated data store

Hi, I'm looking at the possibility of creating a new kind of data store, let's call it a federated data store, and wanted to see what everyone thinks about this. The basic idea is that the federated data store would allow for more than one data store to be configured for an Oak instance. Oak

[jira] [Updated] (JCR-4128) update maven plugins and require Maven 3.2.1

[ https://issues.apache.org/jira/browse/JCR-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4128: Summary: update maven plugins and require Maven 3.2.1 (was: update maven plugins) > update maven

[jira] [Created] (JCR-4128) update maven plugins

Julian Reschke created JCR-4128: --- Summary: update maven plugins Key: JCR-4128 URL: https://issues.apache.org/jira/browse/JCR-4128 Project: Jackrabbit Content Repository Issue Type: Task

BUILD FAILURE: Jackrabbit Oak - Build # 208 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #208) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/208/ to view the results. Changes: [angela] OAK-6092 Find a new home for ApproximateCounter [angela] OAK-6114 : Move InitialContent to

[jira] [Commented] (JCR-4127) update to latest apache parent pom (18)

[ https://issues.apache.org/jira/browse/JCR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15976762#comment-15976762 ] Julian Reschke commented on JCR-4127: - trunk: [r1792066|http://svn.apache.org/r1792066] > update to

[jira] [Resolved] (JCR-4127) update to latest apache parent pom (18)

[ https://issues.apache.org/jira/browse/JCR-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4127. - Resolution: Fixed Fix Version/s: 2.15.2 > update to latest apache parent pom (18) >

[jira] [Created] (JCR-4127) update to latest apache parent pom (18)

Julian Reschke created JCR-4127: --- Summary: update to latest apache parent pom (18) Key: JCR-4127 URL: https://issues.apache.org/jira/browse/JCR-4127 Project: Jackrabbit Content Repository

OAK-6089 (maven plugin updates) and OAK-5664 (require Java 8), also: move to Maven 3.3.9?

Hi there, in preparation of the switch to Java 8, I have updated lots of maven plugin dependencies and also explicitly required the use of Maven 3.2.1 (this is the version we use in CI, and was apparently was also de facto required already). I ran integration tests after each of these

Re: [m12n] Location of InitialContent

On Thu, 2017-04-20 at 08:07 +, Angela Schreiber wrote: > hi > > the original intention of the 'InitialContent' was just to registers > built-in JCR node types, which explains it's location in > org.apache.jackrabbit.oak.plugins.nodetype.write > > in the mean time it has a evolved to

Re: [m12n] A new home for ApproximateCounter, NodeUtil and TreeUtil?

On Wed, 2017-04-19 at 15:53 +, Angela Schreiber wrote: > hi robert > > i created 2 separate tasks in the OAK-6069 m12n epic to track > progress > with ApproximateCounter and NodeUtil|TreeUtil respectively. > moving the ApproximateCounter should be doable with limited effort, > we > just need

BUILD FAILURE: Jackrabbit Oak - Build # 201 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #201) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/201/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak - Build # 200 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #200) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/200/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak - Build # 199 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #199) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/199/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak - Build # 198 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #198) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/198/ to view the results. Changes: [reschke] OAK-6098: update maven plugins maven-assembly-plugin Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak - Build # 197 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #197) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/197/ to view the results. Changes: [angela] minor improvement to oak-commons-run: add private constructor to utilities and remove

Re: [m12n] Location of InitialContent

Hi Julian Yes... having it located where JCR comes into place would be optimal... but not yet possible I guess. That's why I would like to move to a place that contains similar utilities in a first place and then look at everything together again in a second step. Kind regards Angela On

BUILD FAILURE: Jackrabbit Oak - Build # 196 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #196) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/196/ to view the results. Changes: [mduerig] OAK-6106: Excessive memory usage by the caches segment references Test case Test

BUILD FAILURE: Jackrabbit Oak - Build # 195 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #195) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/195/ to view the results. Changes: [alexparvulescu] OAK-3342 move benchmarks in oak-benchmark module - fixed benchmarks scripts

Re: [m12n] Location of InitialContent

Hi Angela >From the features you describe it sounds like it should go into org.apache.jackrabbit.oak.jcr (or at least most of it). It looks like it is being used in lots of tests in oak-core, however, so this may just be wishful thinking... Regards Julian On Thu, Apr 20, 2017 at 10:07 AM,

BUILD FAILURE: Jackrabbit Oak - Build # 194 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #194) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/194/ to view the results. Changes: [reschke] OAK-6098: update maven plugins maven-surefire-plugin Test results: No tests ran.

[m12n] Location of InitialContent

hi the original intention of the 'InitialContent' was just to registers built-in JCR node types, which explains it's location in org.apache.jackrabbit.oak.plugins.nodetype.write in the mean time it has a evolved to container for all kind of initial content required for a JCR repository:

BUILD FAILURE: Jackrabbit Oak - Build # 193 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #193) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/193/ to view the results. Changes: [reschke] OAK-6098: update maven plugins apache-rat-plugin Test results: No tests ran.