On 2017-04-26 10:28, Davide Giannella wrote:
On 26/04/2017 07:57, Julian Reschke wrote:
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...
Are you saying that oak-run generated jar changes size when run with
different profile? If so how is it expected to work as when we're doing
Yes.
a release we're not triggering any specific profile.
Well, in that case we're not triggering the profile, right?
Regardless, the fastest solution is to increase the size according to
what you see. However is this a new dependency you're adding as of new
features?
No, it always has been the case.
However, if you select all RDB profiles you'll include essentially all
JDBC drivers, in which case maintaining the limit becomes pretty
pointless...
Best regards, Julian
