Hi,
On Wed, Mar 23, 2016 at 10:25 AM Davide Giannella wrote:
> Speaking of CI, none of the CIs we currently have in place that I'm
> aware are using such flag. It feels safe therefore to change it.
>
Right, the flag was added for developer convenience, as you could set the
flag in your init scr
On 23/03/2016 11:18, Jukka Zitting wrote:
> See https://issues.apache.org/jira/browse/OAK-163 for original discussion
> about the environment flag.
>
> Back then the integration tests were only just becoming too long to run as
> a part of the regular build, so it made sense to keep that option arou
See https://issues.apache.org/jira/browse/OAK-163 for original discussion
about the environment flag.
Back then the integration tests were only just becoming too long to run as
a part of the regular build, so it made sense to keep that option around
for people who wanted the earlier behavior. But
On 23/03/2016 03:11, Chetan Mehrotra wrote:
> On Tue, Mar 22, 2016 at 9:49 PM, Davide Giannella wrote:
>> I can't really recall why and if we use this.
> Its referred to in main README.md so as to allow a developer to always
> enable running of integration test
>
Thanks Chetan.
Is anyone using th
On Tue, Mar 22, 2016 at 9:49 PM, Davide Giannella wrote:
> I can't really recall why and if we use this.
Its referred to in main README.md so as to allow a developer to always
enable running of integration test
Chetan Mehrotra
hello team
I was trying to achieve https://issues.apache.org/jira/browse/OAK-4136
by enabling multiple profiles using the same property when I stumbled
upon the variable `env.OAK_INTEGRATION_TESTING` for the
`integrationTesting` profile
https://github.com/apache/jackrabbit-oak/blob/8af23571f44055
