" You could argue that it makes the dependency optional" Yes that is what I am saying. Like in a JDBC application you may be connecting to postgres or mysql you are not concerned how those are licensed because you are linked to the shim/driver. You could even bring in the Microsoft SQL server as a jar in this case.
On Fri, May 20, 2016 at 11:21 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 5/20/16, 7:23 AM, "Edward Capriolo" <edlinuxg...@gmail.com> wrote: > > >Would it be acceptable to develop a shim layer toree can link to that and > >the provider is dropped in at runtime like the jdbc interface? > > AIUI, a shim doesn't break the dependency chain. You could argue that it > makes the dependency optional, but then the test becomes whether the > majority of your users will end up downloading the LPGL version anyway. > IMO, the mentors should help you advocate for a second exception to the > rule. > > HTH, > -Alex > >
