I agree with Adrien about assumptions on core and other modules ("core may
not depend on anything (either libraries or other modules) and modules may
not depend on other modules"). Now that we're at it we should probably
check modules that contain "exceptions" and check them on a case by case
On Tue, May 30, 2017 at 4:44 PM, Adrien Grand wrote:
> The dependency convention, as I understand it, is that core may not depend
> on anything (either libraries or other modules) and modules may not depend
> on other modules. Then obviously we have exceptions for practical
5/30/17 18:34:20
> To: dev@lucene.apache.org
> Subject: Re: [DISCUSS] Sandbox module dependencies
>
>
>
> On Tue, May 30, 2017 at 1:18 PM Andrzej Białecki <
> andrzej.biale...@lucidworks.com> wrote:
>
>> Hi,
>>
>> I’m inclined to say “both core
ev@lucene.apache.org
Subject: Re: [DISCUSS] Sandbox module dependencies
On Tue, May 30, 2017 at 1:18 PM Andrzej Białecki
<andrzej.biale...@lucidworks.com> wrote:
Hi,
I’m inclined to say “both core and non-sandbox modules MUST NOT depend on
sandbox”. Otherwise it would mean that regul
On Tue, May 30, 2017 at 1:18 PM Andrzej Białecki <
andrzej.biale...@lucidworks.com> wrote:
> Hi,
>
> I’m inclined to say “both core and non-sandbox modules MUST NOT depend on
> sandbox”. Otherwise it would mean that regular modules, of which users’
> expectations are that they are mostly stable
Hi,
I’m inclined to say “both core and non-sandbox modules MUST NOT depend on
sandbox”. Otherwise it would mean that regular modules, of which users’
expectations are that they are mostly stable and usable, depend on half-baked
experimental stuff with no guarantees whatsoever concerning
Within the Lucene project (not talking about Solr), can Lucene modules
(other than Core) depend on our lucene-sandbox module? I intuitively
assumed "no" but it's purely based on some notion in my head about the role
of sandbox and not because of any prior decision. I figure that
functionality in