Good morning everyone,
when we deal with indexes we can have two use case: synchronous and
asynchronous. In the first use case by being a commit hook the handle
is returned to the application using oak only when all the hooks are
completed and therefore the index is updated.
In the latter
Couple of things to try
* Specify the packages versions via package-info
* Inline the classes instead of embedding the jars
This would enable maven-bundle-plugin to see required
package-info.java file for versions and also the SCR generated files.
Also can you share your project say on github.
On 2014-03-11 16:41, Felix Meschberger wrote:
+1
Coding style is part of the corporate identity of the code, in a sense.
Regards
Felix
...
I like consisting coding style, but then, I also like to be able to
violate a rule in some cases.
That being said: there are more things we should
This is for SLING-3279 which is about improved observation handling when
Oak is available. So I need to check, if Oak is used. In that case I can
use the improved handling and if not, revert to the old code. This allows
to have a single bundle to deploy as 95% of the code is the same.
The tests
In
https://github.com/tteofili/jackrabbit-oak/blob/oak-1475c/oak-solr-osgi/pom.xmlI've
specialized the above approach only for Solr.
Tommaso
2014-03-12 16:40 GMT+01:00 Tommaso Teofili tommaso.teof...@gmail.com:
2014-03-12 12:29 GMT+01:00 Tommaso Teofili tommaso.teof...@gmail.com:
On 12/03/2014 10:36, Tommaso Teofili wrote:
Hi Davide,
in IndexEditorProvider#getIndexEditor you can specify an
IndexUpdateCallback to register for index update notifications, maybe that
can serve your need?
Sorry Tommaso, my ignorance has no limit :)
If I'm a client application that
Hi,
I just noticed that the api exported by the oak-jcr bundle in trunk is 0.16
(trunk version is 0.19-SNAPSHOT). This implies that the api hasn't changed
between the 0.16 release and trunk.
Unfortunately that's not true, as my code does not compile with 0.16, so I
guess the export version needs
Hi
Isn't this new behaviour exposed through API which is not available on non-Oak
systems ? So just trying to instantiate a class implementing that new API would
signal that.
Regards
Felix
Am 12.03.2014 um 17:10 schrieb Carsten Ziegeler cziege...@apache.org:
This is for SLING-3279 which is
Yepp, it's new API - but you never know if just the API bundle is deployed
(for whatever reasons).
Regards
Carsten
2014-03-12 18:00 GMT+01:00 Felix Meschberger fmesc...@adobe.com:
Hi
Isn't this new behaviour exposed through API which is not available on
non-Oak systems ? So just trying to
The Buildbot has detected a new failure on builder oak-trunk while building ASF
Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4651
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4652
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
11 matches
Mail list logo
