I am not a lawyer and you are not likely to find one on this list. That said, the license you choose only applies to your code, not dependencies your code uses. However, users of your code have to consider the ramifications of all the dependencies you use.
But if you are using Logback you almost certainly are using SLF4J as your logging API. SLF4J uses the MIT license, which pretty much allows anyone to do anything. In other words, you will never have a licensing problem with code that uses it. If, for some reason, users aren’t comfortable with the EPL, they can pick other logging frameworks that support SLF4J. But it is very unlikely anyone would have a problem using code that uses the EPL license. Ralph > On Jun 10, 2022, at 7:00 AM, Stefano <[email protected]> wrote: > > Hi all, > > The project is a Java library that contains logback > <https://github.com/qos-ch/logback> as a dependency. > Since logback is published under EPLv1 I'm wondering if I can publish my > project under MIT license. > > What do you think about it? > > Thanks, > Stefano > _______________________________________________ > logback-user mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
