On 17.4.14 3:14 , Jukka Zitting wrote:
Not consistent, correct. The package versions should evolve
semantically based on changed to those specific packages, not in sync
with the broader Oak/Jackrabbit release cycle.
Is there any kind of tooling we could put into place to make this harder
to
Is there any kind of tooling we could put into place to make this harder to
forget?
There's a proposed patch for some tooling in OAK-1536.
Regards
Julian
[OAK-1536]: https://issues.apache.org/jira/browse/OAK-1536
On Tue, Apr 22, 2014 at 8:59 AM, Michael Dürig mdue...@apache.org wrote:
On
Good evening everyone,
(long email warning)
had an offline discussion with Marcel regarding OAK-1717.
Even by having annotating conflicts for the DocumentNS persistence by
implementing OAK-1185 could not suffice for some cases.
https://issues.apache.org/jira/browse/OAK-1717
Hello,
I noticed org.apache.jackrabbit.oak.plugins.document.DocumentMK is not
exported in the OSGi bundle, is there a way to get Oak with the DocumentMK
instantiated in OSGi.
-- Galo
The preferred approach is to instantiate via OSGi configuration. So in
your OSGi create configuration for DocumentNodeStore for pid
'org.apache.jackrabbit.oak.plugins.document.DocumentNodeStoreService'
[1]. This would activate the DocumentNodeStoreService [2] component
and that would register
