logging-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [log4j] Move JDBC appender to own module?
Date Sat, 13 Jan 2018 18:43:29 GMT
I created:

LOG4J2-2188 <https://issues.apache.org/jira/browse/LOG4J2-2188>

Split off JPA support into a new module log4j-jpa
<https://issues.apache.org/jira/browse/LOG4J2-2188>

LOG4J2-2187 <https://issues.apache.org/jira/browse/LOG4J2-2187>

Split off JDBC support into a new module log4j-jdbc
<https://issues.apache.org/jira/browse/LOG4J2-2187>
Gary

On Sat, Jan 13, 2018 at 10:54 AM, Gary Gregory <garydgregory@gmail.com>
wrote:

>
>
> On Jan 13, 2018 09:54, "Mikael Ståldal" <mikes@apache.org> wrote:
>
> As usual, I think we should avoid optional dependencies.
>
>
> That means more modules.
>
> Maybe we can start small here with a log4j-jpa module.
>
> Gary
>
>
>
>
> On 2018-01-13 10:16, Remko Popma wrote:
>
>> I meant to keep the jdbc and the generic db package together.
>>
>> log4j-db:  generic db + jdbc
>> log4j-jpa: requires javax.persistance
>>
>> We can also keep all of these in a single module `log4j-db` with an
>> optional dependency on javax.persistance.
>>
>> More modules gives more flexibility but also more complexity, so I lean
>> towards keeping things together where possible until the flexibility is
>> really needed.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message