Re: Intent to backport to 1.6 OAK-6931

+1 On Tue, Nov 14, 2017 at 12:19 PM, Michael Dürig wrote: > https://issues.apache.org/jira/browse/OAK-6931 > > This fixes an issue in the offline compaction tool, which prevents the cache > size to be set via the command line. > > Michael

BUILD FAILURE: Jackrabbit Oak - Build # 973 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #973) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/973/ to view the results. Changes: [catholicon] OAK-6905: Query engine: support coalesce function as in-built method Implement

BUILD FAILURE: Jackrabbit Oak (ManyChildNodesIT) - Build # 23 - Failure (ManyChildNodesIT)

The Apache Jenkins build system has built Jackrabbit Oak (ManyChildNodesIT) (build #23) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak%20(ManyChildNodesIT)/23/ to view the results. Changes: [catholicon] OAK-6882:

BUILD FAILURE: Jackrabbit Oak - Build # 972 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #972) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/972/ to view the results. Changes: [catholicon] OAK-6882: ObservationQueueFullWarnTest.testQueueFullThenFlushing failing Test

Re: [m12n] Module oak-spi-core defines no export versions

Hi Chetan Well... I would have excepted that one goal of the m12n was to get a clear separation between public API and internals and everything that we target as API/SPI should be public IMO. And I definitely hope that we after that can stop making incompatible changes as that separations allows

Re: [m12n] Module oak-spi-core defines no export versions

Do we want to have explicit version for all packages in oak-core-spi or should we only do it for packages which we expect code outside of Oak codebase would be using? As once we version it we cannot change in backward incompatible way easily Chetan Mehrotra On Tue, Nov 14, 2017 at 10:05 PM,

Re: [m12n] Module oak-spi-core defines no export versions

Hi Robert Ok... I will add 1.0.0 and go ahead tomorrow unless someone objects. Kind regards Angela On 14/11/17 17:23, "Robert Munteanu" wrote: >On Tue, 2017-11-14 at 13:51 +, Angela Schreiber wrote: >> Any preference wrt the initial version number? > >The initial

BUILD FAILURE: Jackrabbit Oak - Build # 971 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #971) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/971/ to view the results. Changes: [angela] OAK-6938 : Add package export version for spi.xml [angela] OAK-6939 : Non-existing package

Re: [m12n] Module oak-spi-core defines no export versions

On Tue, 2017-11-14 at 13:51 +, Angela Schreiber wrote: > Any preference wrt the initial version number? The initial version number should be 1.0.0 IMO. Robert

[m12n] Module oak-spi-core defines no export versions

Hi Devs Looking at OAK-3919 I noticed that most packages in the new _core-spi_ module still don't have export versions properly handled. I guess this is an oversight that we missed during the modularisation. Unless someone objects I would go ahead

Intent to backport to 1.6 OAK-6931

https://issues.apache.org/jira/browse/OAK-6931 This fixes an issue in the offline compaction tool, which prevents the cache size to be set via the command line. Michael