Hi,
On Fri, Mar 9, 2012 at 2:46 PM, Jukka Zitting wrote:
> Makes sense to me too. So, to clarify the intended structure, I draw a
> quick draft of how our components could fit together:
>
> http://people.apache.org/~jukka/2012/oak-overview.png
To expand on this a bit, here's more detailed dia
Author: dpfister
Date: Wed Mar 14 17:38:32 2012
New Revision: 1300657
URL: http://svn.apache.org/viewvc?rev=1300657&view=rev
Log:
Add copying GC for revisions
- completely ignore old revisions in GC cycle
Modified:
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/mk/store/C
[
https://issues.apache.org/jira/browse/OAK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-4:
-
Component/s: run
> Runnable jar packaging
> --
>
> Key: OAK-4
> URL: h
[
https://issues.apache.org/jira/browse/OAK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-9:
-
Component/s: core
> Internal tree builder
> -
>
> Key: OAK-9
> URL: ht
[
https://issues.apache.org/jira/browse/OAK-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-3:
-
Component/s: core
> Internal tree model
> ---
>
> Key: OAK-3
> URL: https:
[
https://issues.apache.org/jira/browse/OAK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-13:
--
Component/s: core
> Cleanup org.apache.jackrabbit.mk
>
>
> Key: OAK-13
[
https://issues.apache.org/jira/browse/OAK-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-12:
--
Component/s: core
> Implement a test suite for the MicroKernel
> --
>
>
[
https://issues.apache.org/jira/browse/OAK-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-11:
--
Component/s: core
> Document and tighten contract of Microkernel API
>
[
https://issues.apache.org/jira/browse/OAK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-6:
-
Component/s: it
> Setup integration tests and TCK tests
> -
>
> Key: O
[
https://issues.apache.org/jira/browse/OAK-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-5:
-
Component/s: jcr
> JCR bindings for Oak
>
>
> Key: OAK-5
> URL: https
Author: dpfister
Date: Wed Mar 14 16:54:33 2012
New Revision: 1300634
URL: http://svn.apache.org/viewvc?rev=1300634&view=rev
Log:
OAK-13 - Cleanup org.apache.jackrabbit.mk
- removed unused packages/classes
- move back json.fast package to test
- remove unused imports in Repository
Added:
jac
On 2012-03-14 16:47, Michael Dürig wrote:
On 14.3.12 14:54, Julian Reschke wrote:
Hi there,
I'm looking at MicroKernel.getNodes(), and I believe the semantics might
perform non-optimal unless we get the property filtering right.
A typical use case always is browsing a repository using a tree
On 14.3.12 14:54, Julian Reschke wrote:
Hi there,
I'm looking at MicroKernel.getNodes(), and I believe the semantics might
perform non-optimal unless we get the property filtering right.
A typical use case always is browsing a repository using a tree view.
A tree view usually needs, given a
Hi,
Somewhat related is that in getJournal, the json diff is "wrapped" as a
json string value. That means the json diff is escaped in the MicroKernel,
and has to be de-escaped on the client.
To avoid this, getJournal could return a json diff that is not wrapped,
but instead matches the json diff
Hi,
>Another problem is the String-fits-all return type; it would make it
>impossible to implement streaming of the result to the client; which
>will make the behavior for large collections non-optimal (the caller
>needs to wait for the complete JSON string to be ready before it can
>start forward
Hi,
On Wed, Mar 14, 2012 at 11:49 AM, Angela Schreiber wrote:
> i would like adjust the JIRA project to reflect the different
> components we are having in the oak project.
Good point.
To get us started I just set up components based on the structure in svn:
https://issues.apache.org/jira/brow
Hi there,
I'm looking at MicroKernel.getNodes(), and I believe the semantics might
perform non-optimal unless we get the property filtering right.
A typical use case always is browsing a repository using a tree view.
A tree view usually needs, given a node N:
- all or a subset of all propert
[
https://issues.apache.org/jira/browse/OAK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229195#comment-13229195
]
Julian Reschke commented on OAK-14:
---
> MVCC wrt. observation: Semantics change somewhat sinc
[
https://issues.apache.org/jira/browse/OAK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229185#comment-13229185
]
Marcel Reutegger commented on OAK-14:
-
> MVCC wrt. observation
another approach that was
[
https://issues.apache.org/jira/browse/OAK-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig reassigned OAK-5:
---
Assignee: Michael Dürig
> JCR bindings for Oak
>
>
> Key: OAK-5
>
[
https://issues.apache.org/jira/browse/OAK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229181#comment-13229181
]
Michael Dürig commented on OAK-14:
--
Here is a list of things we need to keep an eye on. The l
Identify and document changes in behaviour wrt. Jackrabbit 2
Key: OAK-14
URL: https://issues.apache.org/jira/browse/OAK-14
Project: Jackrabbit Oak
Issue Type: Task
Repo
[
https://issues.apache.org/jira/browse/OAK-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-14:
-
Description:
Some implementation specific behaviour will likely change. We should document
the cases, provid
[
https://issues.apache.org/jira/browse/OAK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229161#comment-13229161
]
Thomas Mueller commented on OAK-13:
---
The packages I created:
org.apache.jackrabbit.mk.blobs
[
https://issues.apache.org/jira/browse/OAK-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229144#comment-13229144
]
Dominique Pfister commented on OAK-13:
--
I can comment on the packages/classes I created:
Author: jukka
Date: Wed Mar 14 12:05:02 2012
New Revision: 1300517
URL: http://svn.apache.org/viewvc?rev=1300517&view=rev
Log:
JCR-5: JCR bindings for Oak
Resolve concurrent commits (no need for a duplicate oak-jcr module reference)
Modified:
jackrabbit/oak/trunk/pom.xml
Modified: jackrabbi
Author: angela
Date: Wed Mar 14 11:23:29 2012
New Revision: 1300508
URL: http://svn.apache.org/viewvc?rev=1300508&view=rev
Log:
JCR-5: JCR bindings for Oak
- adjust README.txt
Modified:
jackrabbit/oak/trunk/README.txt
Modified: jackrabbit/oak/trunk/README.txt
URL:
http://svn.apache.org/vi
Author: angela
Date: Wed Mar 14 11:21:46 2012
New Revision: 1300504
URL: http://svn.apache.org/viewvc?rev=1300504&view=rev
Log:
JCR-5: JCR bindings for Oak
- add component to project pom
Modified:
jackrabbit/oak/trunk/pom.xml
Modified: jackrabbit/oak/trunk/pom.xml
URL:
http://svn.apache.o
Author: angela
Date: Wed Mar 14 11:17:06 2012
New Revision: 1300503
URL: http://svn.apache.org/viewvc?rev=1300503&view=rev
Log:
comment system output in ConcurrentWriteTest
Modified:
jackrabbit/oak/trunk/oak-core/src/test/java/org/apache/jackrabbit/mk/ConcurrentWriteTest.java
Modified:
jac
Author: jukka
Date: Wed Mar 14 11:14:50 2012
New Revision: 1300502
URL: http://svn.apache.org/viewvc?rev=1300502&view=rev
Log:
JCR-5: JCR bindings for Oak
Added a dummy OakRepositoryFactory class and a basic CRUD test case.
Include oak-jcr in the main Oak build.
Added:
jackrabbit/oak/trunk/
Author: angela
Date: Wed Mar 14 11:04:08 2012
New Revision: 1300500
URL: http://svn.apache.org/viewvc?rev=1300500&view=rev
Log:
JCR-5: JCR bindings for Oak
- add svn:ignore property
Modified:
jackrabbit/oak/trunk/oak-jcr/ (props changed)
Propchange: jackrabbit/oak/trunk/oak-jcr/
Cleanup org.apache.jackrabbit.mk
Key: OAK-13
URL: https://issues.apache.org/jira/browse/OAK-13
Project: Jackrabbit Oak
Issue Type: Task
Reporter: angela
imo we should clean up the org.apache.jac
hi all
i would like adjust the JIRA project to reflect the different
components we are having in the oak project.
so far i would suggest to create:
- oak core (or mikrokernel)... i am bit confused about the mix here.
- oak jcr
- oak test (including integration testing and benchmark)
we may or
Implement a test suite for the MicroKernel
--
Key: OAK-12
URL: https://issues.apache.org/jira/browse/OAK-12
Project: Jackrabbit Oak
Issue Type: New Feature
Reporter: Michael Dürig
--
Th
Hi,
On Thu, Mar 8, 2012 at 5:45 PM, Jukka Zitting wrote:
> On Thu, Mar 8, 2012 at 2:25 PM, Angela Schreiber wrote:
>> as far as i am concerned i would prefer to have the dev discussions
>> separate from commit messages as the triage is easier.
>
> OK by me. I'll make the request in case there's
Author: reschke
Date: Wed Mar 14 10:12:24 2012
New Revision: 1300492
URL: http://svn.apache.org/viewvc?rev=1300492&view=rev
Log:
Javadoc fixes
Modified:
jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/mk/json/JsopBuilder.java
jackrabbit/oak/trunk/oak-core/src/main/java
[
https://issues.apache.org/jira/browse/OAK-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229112#comment-13229112
]
Jukka Zitting commented on OAK-5:
-
Looks like we have rough consensus to put this into a separa
Author: jukka
Date: Wed Mar 14 09:54:55 2012
New Revision: 1300489
URL: http://svn.apache.org/viewvc?rev=1300489&view=rev
Log:
JCR-5: JCR bindings for Oak
Create oak-jcr component for the JCR binding
Added:
jackrabbit/oak/trunk/oak-jcr/
jackrabbit/oak/trunk/oak-jcr/pom.xml (with props)
38 matches
Mail list logo