Oak 0.2 release plan

Hi, We're getting closer to the end of April and the 0.2 release, so following up from the earlier roadmap [1], here's a list of issues I'd love to see included in the release: * Basic CRUD operations over JCR and HTTP * Extension model for plugging in alternative storage backends * Basic i

[jira] [Created] (OAK-67) Initial OSGi Bundle Setup

Felix Meschberger created OAK-67: Summary: Initial OSGi Bundle Setup Key: OAK-67 URL: https://issues.apache.org/jira/browse/OAK-67 Project: Jackrabbit Oak Issue Type: Improvement Co

Re: Oak 0.2 release plan

Hi, Am 23.04.2012 um 09:33 schrieb Jukka Zitting: > * OSGi bundle packaging I have created OAK-67 [1] to track this and will come up with a patch and recommendations for changes Regards Felix [1] https://issues.apache.org/jira/browse/OAK-67

[jira] [Updated] (OAK-67) Initial OSGi Bundle Setup

[ https://issues.apache.org/jira/browse/OAK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated OAK-67: - Attachment: OAK-67.patch Here is a first shot at a patch. Assumptions (which may be slightly wrong):

Oak Bundles (was : Oak 0.2 release plan)

Hi, So, I attached a patch generating bundles out of the mk, core, and jcr modules. As indicated in the bug I saw a small number of issues: There are a number of problems with the current code structure: * An explicit Export-Package statement is needed in each module because by default the bu

[jira] [Commented] (OAK-67) Initial OSGi Bundle Setup

[ https://issues.apache.org/jira/browse/OAK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259547#comment-13259547 ] Jukka Zitting commented on OAK-67: -- +1 looks good On the last point, instead of using .inter

[jira] [Resolved] (OAK-48) MicroKernel.getNodes() should return null for not existing nodes instead of throwing an exception

[ https://issues.apache.org/jira/browse/OAK-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved OAK-48. --- Resolution: Fixed Implemented the feature in the wrappers and added test cases. > MicroK

[jira] [Created] (OAK-68) Extension point for commit validation

Jukka Zitting created OAK-68: Summary: Extension point for commit validation Key: OAK-68 URL: https://issues.apache.org/jira/browse/OAK-68 Project: Jackrabbit Oak Issue Type: New Feature

oak-API: rename ContentTree to Tree

hi i would like to suggest that we rename ContentTree to Tree. as the Content-prefix looks a bit artificial (and arbitrary) to me. while i see the point in having the ability to distinguish jcr-Session from oak-Session and jcr-Repository from oak-Repository, i fail to see the benefit for the Con

Re: oak-API: rename ContentTree to Tree

On 23.4.12 13:33, Angela Schreiber wrote: hi i would like to suggest that we rename ContentTree to Tree. as the Content-prefix looks a bit artificial (and arbitrary) to me. while i see the point in having the ability to distinguish jcr-Session from oak-Session and jcr-Repository from oak-Repos

Proposal for Value Handling (oak-jcr and oak-core)

hi all as discussed recently in revision rev. 1329281 [1] i added a new implementation of ValueFactory and Value/Binary in oak-jcr that is based on value handling exposed by oak-api. my goal was to address both the needs from jcr (API contract) and oak-core (ability to detect value types for val

Re: Proposal for Value Handling (oak-jcr and oak-core)

corrigenda: rev. 1329281 Revision: 1329293 URL: http://svn.apache.org/viewvc?rev=1329293&view=rev :)

[jira] [Created] (OAK-69) oak-run fails with NPE

Jukka Zitting created OAK-69: Summary: oak-run fails with NPE Key: OAK-69 URL: https://issues.apache.org/jira/browse/OAK-69 Project: Jackrabbit Oak Issue Type: Bug Components: run

[jira] [Commented] (OAK-67) Initial OSGi Bundle Setup

[ https://issues.apache.org/jira/browse/OAK-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260289#comment-13260289 ] Felix Meschberger commented on OAK-67: -- I am ok with just exportin .api. But what about .