+1 for initializing the default config unconditionally
Regards
Julian
On Fri, Oct 21, 2016 at 12:14 PM, Chetan Mehrotra
wrote:
> Opened OAK-4975 for query around default config handling.
> Chetan Mehrotra
>
>
> On Fri, Oct 21, 2016 at 2:14 PM, Davide Giannella wrote:
>> On 21/10/2016 08:23, Mic
Opened OAK-4975 for query around default config handling.
Chetan Mehrotra
On Fri, Oct 21, 2016 at 2:14 PM, Davide Giannella wrote:
> On 21/10/2016 08:23, Michael Marth wrote:
>> Hi Chetan,
>>
>> Re “Should we ship with a default config”:
>>
>> I vote for a small default config:
>> - default beca
On 21/10/2016 08:23, Michael Marth wrote:
> Hi Chetan,
>
> Re “Should we ship with a default config”:
>
> I vote for a small default config:
> - default because: if the feature is always-on in trunk we will get better
> insights in day-to-day work (as opposed to switching it on only occasionally)
Hi Chetan,
Re “Should we ship with a default config”:
I vote for a small default config:
- default because: if the feature is always-on in trunk we will get better
insights in day-to-day work (as opposed to switching it on only occasionally)
- small because: the optimal bundling is probably very
Hi Team,
Work for OAK-1312 is now in trunk. To enable this feature user has to
provision some config as content in repository. The config needs to be
created under '/jcr:system/rep:documentStore/bundlor' [1]
Example
-
jcr:system
rep:documentStore
bundlor
app:Asset{pattern = [jcr:c
