Re: No more log4j-nosql

2017-10-19 Thread Matt Sicker
WRT to Cassandra, the best I can do is that integration test I added with the plugin. My Cassandra cluster at $job is pretty restricted since improper usage of said cluster could bankrupt the business in theory. On 19 October 2017 at 19:29, Gary Gregory wrote: > WRT MongoDB, please see my other

Re: No more log4j-nosql

2017-10-19 Thread Gary Gregory
WRT MongoDB, please see my other email "Testing log4j-mongodb". Thank you, Gary On Thu, Oct 19, 2017 at 2:02 PM, Mikael Ståldal wrote: > If someone has a running MongoDB, CouchDB or Cassandra handy, some manual > testing would be good. > > Especially for MongoDB and CouchDB since we don't have

Re: No more log4j-nosql

2017-10-19 Thread Mikael Ståldal
If someone has a running MongoDB, CouchDB or Cassandra handy, some manual testing would be good. Especially for MongoDB and CouchDB since we don't have any unit tests. There are some ignored integration tests for MongoDB. On 2017-10-19 21:52, Mikael Ståldal wrote: I have now done https://is

No more log4j-nosql

2017-10-19 Thread Mikael Ståldal
I have now done https://issues.apache.org/jira/browse/LOG4J2-2076 splitting up log4j-nosql into its three parts. We should mention in release notes in next release that those who use log4j-nosql need to change dependency to one (or more) of log4j-couchdb, log4j-mongodb or log4j-cassandra instea