[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender
[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205320#comment-16205320 ] Ralph Goers commented on LOG4J2-2076: - I wasn't thinking that nosql would generate a jar. I would have no problem with those classes being under appender.nosql in core. I was just thinking I wouldn't want to have all 3 directories at the root level. > Split up log4j-nosql into one module per appender > - > > Key: LOG4J2-2076 > URL: https://issues.apache.org/jira/browse/LOG4J2-2076 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.9.1 >Reporter: Mikael Ståldal > > The log4j-nosql module contains an arbitrary collection of appenders for > MongoDB, CouchDB and Cassandra. It should be split up into one module for > each appender. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender
[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205309#comment-16205309 ] Matt Sicker commented on LOG4J2-2076: - It could be. All the classes directly in this package: https://github.com/apache/logging-log4j2/tree/master/log4j-nosql/src/main/java/org/apache/logging/log4j/nosql/appender could be either moved to log4j-core, or they could be their own module that essentially provides some abstract base classes common to other NoSQL appenders. > Split up log4j-nosql into one module per appender > - > > Key: LOG4J2-2076 > URL: https://issues.apache.org/jira/browse/LOG4J2-2076 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.9.1 >Reporter: Mikael Ståldal > > The log4j-nosql module contains an arbitrary collection of appenders for > MongoDB, CouchDB and Cassandra. It should be split up into one module for > each appender. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender
[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205301#comment-16205301 ] Ralph Goers commented on LOG4J2-2076: - Does it make sense to make nosql a multi-module parent for these 3 projects? > Split up log4j-nosql into one module per appender > - > > Key: LOG4J2-2076 > URL: https://issues.apache.org/jira/browse/LOG4J2-2076 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.9.1 >Reporter: Mikael Ståldal > > The log4j-nosql module contains an arbitrary collection of appenders for > MongoDB, CouchDB and Cassandra. It should be split up into one module for > each appender. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LOG4J2-2076) Split up log4j-nosql into one module per appender
[ https://issues.apache.org/jira/browse/LOG4J2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205300#comment-16205300 ] Matt Sicker commented on LOG4J2-2076: - You may want to move some of the common code back in to log4j-core while you're at it. I did that with ColumnMapping already. > Split up log4j-nosql into one module per appender > - > > Key: LOG4J2-2076 > URL: https://issues.apache.org/jira/browse/LOG4J2-2076 > Project: Log4j 2 > Issue Type: Improvement > Components: Appenders >Affects Versions: 2.9.1 >Reporter: Mikael Ståldal > > The log4j-nosql module contains an arbitrary collection of appenders for > MongoDB, CouchDB and Cassandra. It should be split up into one module for > each appender. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
