That escalated and de-escalated quickly! ---------- Forwarded message ---------- From: Sebastian Oerding (JIRA) <j...@apache.org> Date: 2 July 2014 11:51 Subject: [jira] [Resolved] (LOG4J2-697) Self written Appender stopped working To: log4j-dev@logging.apache.org
[ https://issues.apache.org/jira/browse/LOG4J2-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Oerding resolved LOG4J2-697. -------------------------------------- Resolution: Fixed Fix Version/s: 2.0-rc2 Activated annotation processing on wrong project. Sorry. > Self written Appender stopped working > ------------------------------------- > > Key: LOG4J2-697 > URL: https://issues.apache.org/jira/browse/LOG4J2-697 > Project: Log4j 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.0-rc2 > Environment: Eclipse 4.3 on Windows 7 Professional 64 bit, some 1.6_0_X JDK with x > 43. > Reporter: Sebastian Oerding > Priority: Critical > Fix For: 2.0-rc2 > > Attachments: TranslogAppender.java, log4j2.xml, log4jStartUpLog.txt > > > We had a self written appender which stopped working when switching from rc-1 to rc-2. > I tried to enable Annoation Processing in Eclipse as I assume that this is due to changed stuff around the Log4j2Plugins.dat. However I get no hint that the annotations are actually processed. Windows finds no new file on system (but even fails to find the existing Log4j2Plugins.dat). Furthermore setting the status in the configuration to "trace" I got the impression that only the Log4j2Plugins.dat from the log4j2 jar is loaded. > I'm not sure whether this is really a critical issue for more users, for us it is a blocker. Taking the problems into account we had with Log4j2 so far (memory leaks, API breaks, ...) we are wondering whether it is worth to completely write the logging by ourselves and get rid of log4j2 or switch back to something like SLF4j. -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- Matt Sicker <boa...@gmail.com>