Sry for my stupid questions :)...I will check my project again ----- Reply message ----- Von: "Matt Sicker" <[email protected]> An: "Log4J Developers List" <[email protected]> Betreff: Splitting off NoSQL to its own module. Datum: Mo., Mai 5, 2014 18:51
You just need log4j-core as a dependency when you compile. By default, it will invoke the plugin processor to generate that .dat file.. On 5 May 2014 11:49, [email protected] <[email protected]> wrote: Do I understand the process right? At compile time of log4j-nosql all nosql based appender must be known? Does it mean that I never could implement a new appender if I do not have the sources? ----- Reply message ----- Von: "Matt Sicker" <[email protected]> An: "Log4J Developers List" <[email protected]>, "Markus Klose" <[email protected]> Betreff: Splitting off NoSQL to its own module. Datum: Mo., Mai 5, 2014 18:32 You are adding log4j-nosql to your deployment or classpath, right? When log4j-nosql is compiled, the Log4j2plugins.dat file is created by an annotation processor. In a typical environment, the classpath is scanned for all the resource files with the correct name and path. Are you getting any relevant status log output for the plugins? On 5 May 2014 10:15, Markus Klose <[email protected]> wrote: Hi, since you moved the nosql appender into a separate module some of my other test are failing. I have a test that reads a log4j.xml, getting a specific logger and getting all appenders of that specific logger. but now this test does not have any (nosql) appender anymore in my output i have seen the following line 2014-05-05 17:02:38,127 DEBUG Found Plugin Map at file:/C:/Users/mk/git/logging-log4j2/log4j-core/target/classes/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat Log4j2Plugins.dat does not contain any nosql stuff. Could this file be realted to my problem? Do i need to change the log4j.xml to cache that appender as well? below you will find the log4j.xml I am using. <?xml version="1.0" encoding="UTF-8"?> <Configuration status="DEBUG"> <Appenders> <Console name="Console" target="SYSTEM_OUT"> <PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"/> </Console> <NoSql name="HttpSolrServerAppender"> <Solr url="http://localhost:8983/solr"; commitWithinMs="1000"/> </NoSql> <NoSql name="databaseAppender"> <MongoDb collectionName="applicationLog" factoryClassName="org.example.db.ConnectionFactory" factoryMethodName="getNewMongoClient" /> </NoSql> </Appenders> <Loggers> <Root level="DEBUG"> <AppenderRef ref="Console" level="DEBUG"/> </Root> <Logger name="HttpSolrServer" level="DEBUG"> <AppenderRef ref="HttpSolrServerAppender"/> <AppenderRef ref="databaseAppender"/> </Logger> </Loggers> </Configuration> Matt Sicker <[email protected]> hat am 4. Mai 2014 um 18:38 geschrieben: Good point. I'm renaming it to org.apache.logging.log4j.nosql.appender. Committed in r1592377. On 4 May 2014 03:07, Markus Klose <[email protected]> wrote: does it makes sense to refactorr the package wihtin the module "log4-nosql" as well actually the package is still "org.apache.logging.log4j.core.appender" but its not core anymore Markus Matt Sicker < [email protected]> hat am 29. April 2014 um 00:49 geschrieben: After some basic discussion about this, I'm going to split off the NoSQL code into a module called "log4j-nosql". This is where the Mongo and Couch plugins are right now, and it looks like we'll be adding a Solr one soon most likely along with that Gora one. Anyway, I split it out last night but didn't get a chance to test it out until just now. All tests still pass, so I'm going to commit it. If there are any objections, I can roll back this commit. -- Matt Sicker < [email protected]> -- Matt Sicker < [email protected]> -- Matt Sicker <[email protected]> -- Matt Sicker <[email protected]>
