On 18/11/2014 11:00, Michael Dürig wrote:
On 18.11.14 9:56 , Davide Giannella wrote:
I think that now the procedure for fully update the javadoc and website
should be the following:
oak-doc$ mvn clean site
reactor$ mvn site -P site-with-javadoc
(tested locally and works)
reactor$ mvn
How to get buildbot working again. I am not sure on what steps are
required (or how buildbot is managed) so any pointers on that would be
helpful
Chetan Mehrotra
On Mon, Nov 17, 2014 at 7:39 PM, Davide Giannella dav...@apache.org wrote:
On 17/11/2014 11:24, Chetan Mehrotra wrote:
For past some
I think it is through INFRA issues.
Michael
On 19.11.14 12:40 , Chetan Mehrotra wrote:
How to get buildbot working again. I am not sure on what steps are
required (or how buildbot is managed) so any pointers on that would be
helpful
Chetan Mehrotra
On Mon, Nov 17, 2014 at 7:39 PM, Davide
I see the buildbot at work [0] [1], maybe we just need to ask infra about
the status emails?
alex
[0] http://ci.apache.org/builders/oak-trunk
[1] http://ci.apache.org/builders/oak-trunk-win7
On Wed, Nov 19, 2014 at 1:37 PM, Michael Dürig mdue...@apache.org wrote:
I think it is through
Following up on the earlier mail thread [1] but focusing on fulltext
parsing happening at the Query Engine level
Consider a case where we search for mountain is big and assume that
no aggregation complexity is involved
/jcr:root/content//element(*, test:Asset)[(jcr:contains(., 'mountain is
On Wed, Nov 19, 2014 at 6:09 PM, Alex Parvulescu
alex.parvule...@gmail.com wrote:
I see the buildbot at work [0] [1], maybe we just need to ask infra about
the status emails?
Thats better. Have raised infra issue INFRA-8659 for that
Chetan Mehrotra
On 19/11/2014 13:23, Chetan Mehrotra wrote:
...
So should we disable the Fulltext parsing happening in QueryEngine?
I think we should reproduce and OOTB behaviour as it was in JR2 as
customer updating from that will expect the same behaviour.
So I would ensure about what that behaviour is and
