I agree that it would not be a good idea to move things into log4j-core, it has too many optional dependencies already.
On Fri, Sep 30, 2016 at 6:51 PM, Ralph Goers (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/LOG4J2-1626?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=15536451#comment-15536451 ] > > Ralph Goers commented on LOG4J2-1626: > ------------------------------------- > > I created LOG4J2-1627. Moving things back into core is counterproductive > as it doesn't speed up the build. Instead, I would look at core for things > that might be moved out. > > > Port Windows Event Log Appender from Log4j 1.2 > > ---------------------------------------------- > > > > Key: LOG4J2-1626 > > URL: https://issues.apache.org/jira/browse/LOG4J2-1626 > > Project: Log4j 2 > > Issue Type: New Feature > > Components: Appenders > > Reporter: Gary Gregory > > Assignee: Gary Gregory > > > > Log4j 1.2 had an Windows Event Log Appender event log appender. Port it > to Log4j 2. This was the NTEventLogAppender and associated DLL. Provide > both a 32-bit and 64-bit DLL. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- [image: MagineTV] *Mikael Ståldal* Senior software developer *Magine TV* [email protected] Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com Privileged and/or Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such a person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email.
