Hi Robert
plugins.tree would feel natural to me.
regarding the export: not sure about that either... the plugins.tree has
some unfortunate dependencies e.g. to oak.core. so probably more work
ahead in that area.
kind regards
angela
On 06/04/17 16:41, "Robert Munteanu"
Hi,
Working in the m12n branch [1] I'm trying to get rid of the
o.a.j.oak.util package and the last surviving members are
ApproximateCounter, NodeUtil and TreeUtil.
As I see it these classes are essentially helpers built on top of the
Tree and NodeState APIs. Those would make them candidates on
yes, sorry, my bad for not having provided the right context.
in such context oak-commons would contain plain utility class which are not
oak specific (no dependency on org.apache.jackrabbit.oak..) while oak-base
would contain utility classes that relate to oak specific stuff.
Regards,
Tommaso
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release:
Release Notes -- Apache Jackrabbit Oak --
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak. The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release:
Release Notes -- Apache Jackrabbit Oak --
Hello Team,
the vote passes as follows:
+1 Julian Reschke
+1 Alex Parvulescu
+1 Davide Giannella
Thanks for voting. I'll push the release out.
-- Davide
[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958919#comment-15958919
]
Csaba Varga commented on JCR-4126:
--
Hi Julian,
No, this is definitely not an emergency. The errors in the
[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958913#comment-15958913
]
Julian Reschke commented on JCR-4126:
-
That would be Jackrabbit 2.12.*, which we happened to release
hi davide
actually we don't have oak-base :-)
the mail might be a bit out of context... we only have it in a poc.
you may want to take a look at that initial draft
https://github.com/mreutegg/jackrabbit-oak/tree/m12n
but please note that it is still heavily under construction... basically
we
On 06/04/2017 11:11, Tommaso Teofili wrote:
> (and eventually oak-commons / oak-base)
I wasn't aware of oak-base. What about a bundle oak-api which exports
the APIs on which other bundles should rely on?
D.
[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958891#comment-15958891
]
Csaba Varga commented on JCR-4126:
--
Also, if it's not too much to ask, can we get this fix backported to
[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Varga updated JCR-4126:
-
Attachment: concurrent-datastore-fix.diff
I'm attaching a patch that should fix the issue, and also
[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Varga updated JCR-4126:
-
Status: Patch Available (was: Open)
> Shared FileDataStore throws exception if two processes try to add
Csaba Varga created JCR-4126:
Summary: Shared FileDataStore throws exception if two processes
try to add the same file concurrently
Key: JCR-4126
URL: https://issues.apache.org/jira/browse/JCR-4126
On Thu, 2017-04-06 at 10:11 +, Tommaso Teofili wrote:
> Hi all,
>
> as part of refactoring and making more appropriate interdependencies
> I
> think it'd be good if we could have that oak-blob-* modules depend on
> just
> oak-blob (and eventually oak-commons / oak-base) and cut their
>
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958706#comment-15958706
]
Manfred Baedke commented on JCR-4125:
-
See org.apache.jackrabbit.core.data.db.mssql.properties in
Hi all,
as part of refactoring and making more appropriate interdependencies I
think it'd be good if we could have that oak-blob-* modules depend on just
oak-blob (and eventually oak-commons / oak-base) and cut their dependency
to oak-core so that they would only rely on the purposely exposed
I agree it's a good idea to move it.
alex
On Thu, Apr 6, 2017 at 9:50 AM, Angela Schreiber wrote:
> Hi
>
> To me it looks odd that the OakInitializer utility is located in
> org.apache.jackrabbit.oak.spi.lifecycle.
> It is only used the by the Oak utility and by some test
[
https://issues.apache.org/jira/browse/JCR-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-4124.
-
Resolution: Fixed
> Release Jackrabbit 2.12.7
> -
>
> Key:
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.12.7. The release is available for download at:
https://jackrabbit.apache.org/jcr/downloads.html#v2.12
See the full release notes below for details about this release:
Release Notes -- Apache
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.12.7. The release is available for download at:
https://jackrabbit.apache.org/jcr/downloads.html#v2.12
See the full release notes below for details about this release:
Release Notes -- Apache
Hi,
On Thu, Apr 6, 2017 at 12:41 PM, Angela Schreiber wrote:
> Can we move to a package that properly reflects the fact that it is
> intended to be used by NodeStore implementations (segment-tar,
> document-store)?
>
+1
Thanks
Amit
On 06/04/2017 08:50, Angela Schreiber wrote:
> Any objection against moving it to org.apache.jackrabbit.oak to reside
> along with the Oak utility?
+1
Davide
On 06/04/2017 08:11, Angela Schreiber wrote:
> Consequently, I have the impression that it is misplaced in the
> o.a.j.oak.plugins.identifier package, which is intended to contain classes
> related to JCR uuid and identifier handling.
>
> Can we move to a package that properly reflects the fact
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958539#comment-15958539
]
Julian Reschke commented on JCR-4125:
-
Sorry -- I don't know that part of the code. You probably have to
Hi
To me it looks odd that the OakInitializer utility is located in
org.apache.jackrabbit.oak.spi.lifecycle.
It is only used the by the Oak utility and by some test setups.
Any objection against moving it to org.apache.jackrabbit.oak to reside
along with the Oak utility?
Kind regards
Angela
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958464#comment-15958464
]
Shashank commented on JCR-4125:
---
[~reschke] Thanks for your reply. How do I find out which table the uploaded
Hi
While working on an initial PoC to modularise the Oak code base, I noticed
the utility class ClusterRepositoryInfo.
This class (only containing a single static method) is only used by
NodeStore implementations and only depends on low level interfaces/classes.
Consequently, I have the
Hi there,
the vote passes as follows:
+1 Amit Jain
+1 Claus Köll
+1 Julian Reschke
Thanks for voting. I'll push the release out.
Best regards, Julian
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958417#comment-15958417
]
Julian Reschke commented on JCR-4125:
-
Might be a simple type overflow, a JDBC restriction, or a DB
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Affects Version/s: (was: 2.0)
2.12.4
> Not able to upload a large file (2 GB) via
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Affects Version/s: 2.0
> Not able to upload a large file (2 GB) via Jackrabbit to an MS SQL Server
> 2014
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Fix Version/s: (was: 2.0)
> Not able to upload a large file (2 GB) via Jackrabbit to an MS SQL Server
> 2014
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Description:
I have configured my Jackrabbit to store repository on an MS SQL Server 2014
Database. When I
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Description:
I have configured my Jackrabbit to store repository on an MS SQL Server 2014
Database. When I
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Description:
I have configured my Jackrabbit to store repository on an MS SQL Server 2014
Database. When I
[
https://issues.apache.org/jira/browse/JCR-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank updated JCR-4125:
--
Description:
I have configured my Jackrabbit to store repository on an MS SQL Server 2014
Database. When I
Shashank created JCR-4125:
-
Summary: Not able to upload a large file (2 GB) via Jackrabbit to
an MS SQL Server 2014 Database.
Key: JCR-4125
URL: https://issues.apache.org/jira/browse/JCR-4125
Project:
38 matches
Mail list logo