Re: Oak 1.3.16 release plan

2016-02-12 Thread Stefan Egli 
Hi Davide,

As mentioned on the list OAK-4006 is in discussion and in the works. So,
depending on the outcome it might require a small delay.

Cheers,
Stefan

On 11/02/16 11:45, "Davide Giannella"  wrote:

>Hello team,
>
>I'm planning to cut Oak 1.3.16 on Monday 15th February more or less 10am
>GMT.
>
>If there are any objections please let me know. Otherwise I will
>re-schedule any non-resolved issue for the next iteration.
>
>Thanks
>Davide
>
>

Re: Oak 1.3.16 release plan

2016-02-12 Thread Davide Giannella 
On 12/02/2016 12:03, Stefan Egli wrote:
> Hi Davide,
>
> As mentioned on the list OAK-4006 is in discussion and in the works. So,
> depending on the outcome it might require a small delay.
>
Sure not a problem. Ping me directly when done so that we can short-cut
any delays.

Cheers
Davide

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.27

2016-02-12 Thread Dominique Jaeggi 
Hi,

The vote passes as follows:

+1 Julian Reschke
+1 Alex Parvulescu
+1 Amit Jain
+1 Dominique Jaeggi

Thanks for voting. I'll push the release out.

Regards
Dom.

oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

2016-02-12 Thread Davide Giannella 
Team,

the build is constantly failing on my local with (oak-upgrade)

Failed tests:  
referencedOlderThanOrphaned(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
No history found for /versionables/mix:simpleVersionable/old
 
copyAllVersions(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
Node /versionables/mix:simpleVersionable/old should have mix:versionable
mixin
 
onlyReferencedAfterDate(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
No history found for /versionables/mix:simpleVersionable/young
 
onlyReferenced(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest): No
history found for /versionables/mix:simpleVersionable/old
 
referencedSinceDate(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
Node /versionables/mix:simpleVersionable/young should have
mix:versionable mixin

Can anyone give a look as it will be a blocker for next Monday release?

Cheers
Davide

[ANNOUNCE] Apache Jackrabbit Oak 1.0.27 released

2016-02-12 Thread Dominique Jaeggi 
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.0.26 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 -- Version 1.0.27

Introduction


Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

Apache Jackrabbit Oak 1.0.27 is a patch release that contains fixes and
improvements over Oak 1.0. Jackrabbit Oak 1.0.x releases are considered
stable and targeted for production use.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

Changes in Oak 1.0.27
-

Technical task

   [OAK-3896] - RDBDocumentStore: export tool - improve handling of
export files allowing to override column order
   [OAK-3945] - RDBDocumentStore: internalCreateOrUpdate() needs to
check return code of insertDocuments()
   [OAK-3971] - RDBDocumentStore: include table name when logging
slow/excessive queries

Bug

   [OAK-3821] - Lucene directory: improve exception messages
   [OAK-3911] - Integer overflow causing incorrect file handling in
OakDirectory for file size more than 2 GB
   [OAK-3932] - DocumentStore.getIfCached() must not return NodeDocument.NULL
   [OAK-3968] - Wrong initialization of used/ignored properties from
OSGi configuration
   [OAK-3974] - regression:
OakSolrConfigurationProviderService.activate can throw a NPE
   [OAK-3981] - Change in aggregation flow in OAK-3831 causes some
properties to be left out of aggregation

Improvement

   [OAK-3126] - Enable HybridMapFactory by default
   [OAK-3527] - Improve logging for blob GC
   [OAK-3918] - Include index details in exception thrown by OakDirectory
   [OAK-3936] - [oak-run] Option to dump blob references
   [OAK-3990] - Enable specifying the max clause limit in BooleanClause

Task

   [OAK-2937] - Remove code related to directmemory for off heap caching
   [OAK-3613] - Backport TarMK revision gc related issues


In addition to the above-mentioned changes, this release contains
all changes included in previous Apache Jackrabbit Oak 1.0.x releases.

Please note, the backported RDB support for the DocumentNodeStore is considered
experimental at this point and is not yet ready for production use. Feel free
to try it out and report any issues you may see to the Oak developers.

For more detailed information about all the changes in this and other
Oak releases, please see the Oak issue tracker at

  https://issues.apache.org/jira/browse/OAK

Release Contents


This release consists of a single source archive packaged as a zip file.
The archive can be unpacked with the jar tool from your JDK installation.
See the README.md file for instructions on how to build this release.

The source archive is accompanied by SHA1 and MD5 checksums and a PGP
signature that you can use to verify the authenticity of your download.
The public key used for the PGP signature can be found at
http://www.apache.org/dist/jackrabbit/KEYS.

About Apache Jackrabbit Oak
---

Jackrabbit Oak is a scalable, high-performance hierarchical content
repository designed for use as the foundation of modern world-class
web sites and other demanding content applications.

The Oak effort is a part of the Apache Jackrabbit project.
Apache Jackrabbit is a project of the Apache Software Foundation.

For more information, visit http://jackrabbit.apache.org/oak

About The Apache Software Foundation


Established in 1999, The Apache Software Foundation provides organizational,
legal, and financial support for more than 140 freely-available,
collaboratively-developed Open Source projects. The pragmatic Apache License
enables individual and commercial users to easily deploy Apache software;
the Foundation's intellectual property framework limits the legal exposure
of its 3,800+ contributors.

For more information, visit http://www.apache.org/

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

2016-02-12 Thread Davide Giannella 
On 12/02/2016 16:39, Julian Reschke wrote:
> It seems this was caused by switching to Jackrabbit 2.12.0.
>
> Reverting http://svn.apache.org/viewvc?rev=1730031=rev might
> unblock the release, but of course we'll still need to find out what
> Jackrabbit change caused the regression, why that wasn't catched by
> Jackrabbit tests, fix that, and make a new Jackrabbit release...

ok. We'll need a stable JR into Oak for 1.4. Honestly I'd rather delay
the 1.3.16 a couple of days for a proper fix so that we'll have longer
coverage in oak with the JR 2.12 branch.

The bug came indeed out after my inclusion of JR 2.12 which highlights
how coupled JR and Oak are; and that with the current approach we need a
reliable continuous build of JR SNAPSHOT and Oak SNAPSHOT to early catch
regressions.

Davide

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

2016-02-12 Thread Julian Reschke 

On 2016-02-12 16:00, Davide Giannella wrote:

Team,

the build is constantly failing on my local with (oak-upgrade)

Failed tests:
referencedOlderThanOrphaned(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
No history found for /versionables/mix:simpleVersionable/old

copyAllVersions(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
Node /versionables/mix:simpleVersionable/old should have mix:versionable
mixin

onlyReferencedAfterDate(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
No history found for /versionables/mix:simpleVersionable/young

onlyReferenced(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest): No
history found for /versionables/mix:simpleVersionable/old

referencedSinceDate(org.apache.jackrabbit.oak.upgrade.CopyVersionHistoryTest):
Node /versionables/mix:simpleVersionable/young should have
mix:versionable mixin

Can anyone give a look as it will be a blocker for next Monday release?

Cheers
Davide


It seems this was caused by switching to Jackrabbit 2.12.0.

Reverting http://svn.apache.org/viewvc?rev=1730031=rev might 
unblock the release, but of course we'll still need to find out what 
Jackrabbit change caused the regression, why that wasn't catched by 
Jackrabbit tests, fix that, and make a new Jackrabbit release...


Best regards, Julian

DocumentStore question.

2016-02-12 Thread Ian Boston 
Hi,
I am looking at [1], and probably confused.

Is there an assumption that the revisions listed in _revisions are ordered ?

If not, then how is the order of the revisions be determined, given that
the clocks on each node in a cluster will have different offsets ?

Best Regards
Ian


1 http://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html

Anchor tags on doc pages get positioned wrongly under top menu

2016-02-12 Thread Vikas Saurabh 
Hi,

I'm sure we all have noticed that our anchor tags scroll the page a
little too much such that the actual position gets hidden under the
same menu.

With google and this link [0], it seems, we can just plug-in

```
:target:before {
content:"";
display:block;
height:40px; /* fixed header height*/
margin:-40px 0 0; /* negative fixed header height */
}
```
in oak-doc/src/site/resources/site.css to fix the issue.

But, since I suck at html/css, I wasn't sure if this is fine. '40px'
is manual hit-and-trial. Is there something better?

Thanks,
Vikas

[0]: 
https://www.itsupportguides.com/tech-tips-tricks/how-to-offset-anchor-tag-link-using-css/

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

2016-02-12 Thread Manfred Baedke 

Hi,

This is due to change 1721196 (associated with JCR-2633), which changes 
the persistent data model. Probably the test has just to be tweaked 
accordingly, I'll look into it during WE.


Best regards,
Manfred

On 2/12/2016 5:50 PM, Davide Giannella wrote:

On 12/02/2016 16:39, Julian Reschke wrote:

It seems this was caused by switching to Jackrabbit 2.12.0.

Reverting http://svn.apache.org/viewvc?rev=1730031=rev might
unblock the release, but of course we'll still need to find out what
Jackrabbit change caused the regression, why that wasn't catched by
Jackrabbit tests, fix that, and make a new Jackrabbit release...

ok. We'll need a stable JR into Oak for 1.4. Honestly I'd rather delay
the 1.3.16 a couple of days for a proper fix so that we'll have longer
coverage in oak with the JR 2.12 branch.

The bug came indeed out after my inclusion of JR 2.12 which highlights
how coupled JR and Oak are; and that with the current approach we need a
reliable continuous build of JR SNAPSHOT and Oak SNAPSHOT to early catch
regressions.

Davide