That is what is concerning. A lot of those items have already been moved to their own modules in master. Yet we still have these dependencies.
Ralph > On Apr 13, 2021, at 10:53 AM, Jochen Wiedmann <jochen.wiedm...@gmail.com> > wrote: > > On Tue, Apr 13, 2021 at 5:44 PM Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> We also have dependencies on things like java.rmi, java.naming, java.sql. I >> am also not clear on whether they are all really optional or not. Ideally, >> the only required dependency we should have is for java.base. > > Most likely, those dependencies are related to specific appenders, > like, the JDBCAppender, and similar stuff. This could be resolved by > > a) Moving those appenders to separately distributable, and > optional, modules, and > b) Enhance the plugin mechanism to detect, and (if necessary) > initialize such modules automatically, > > As a result, we could have a core, which behaves just like before, if > those modules are present in the classpath. > > Jochen > > -- > > Look, that's why there's rules, understand? So that you think before > you break 'em. > > -- (Terry Pratchett, Thief of Time) >
