+1 for failing a build as warnings at times go unnoticed. If it breaks
we can analyze what got pulled in and then we can raise the limit
Chetan Mehrotra


On Fri, Apr 21, 2017 at 7:09 PM, Davide Giannella <dav...@apache.org> wrote:
> Hello team,
>
> in order to not ending up again with a very big oak-run I would like to
> introduce and enforcement in the size at a value I didn't investigate yet.
>
> I don't mean to introduce it as a blocker but more a warning. if by
> adding a feature it starts getting too big we can simply try to
> understand what we could do. Can we do anything different or shall we
> simply increase the size?
>
> Thoughts?
>
> Davide
>

Reply via email to