On 2017-04-21 15:39, Davide Giannella 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?
Turns out to be problematic when testing with RDB, as the various
profiles include the JDBC drivers, and even with -Prdb-derby, the size
is already exceeded...
Best regards, Julian
