As for SQL, the JDBC one doesn't have any dependencies, so that could stay in core if desired, but the JPA one does require additional Java EE APIs, so that'd make sense to separate at the very least.
As for the nosql ones, again, it would be nice to split those up so that there aren't optional dependencies. That would either mean a mongo and couch component, or it could also mean an additional nosql-common component (unless the abstract classes were put into log4j-core). On 4 December 2016 at 12:44, Gary Gregory <garydgreg...@gmail.com> wrote: > Thoughts on splitting out SQL and MOM (JMS) into their own modules? We > already have a nosql module, having a sql one makes sense. The overall idea > is to make core lighter. > -- Matt Sicker <boa...@gmail.com>
