[
https://issues.apache.org/jira/browse/LOG4J2-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535106#comment-15535106
]
Gary Gregory edited comment on LOG4J2-1626 at 9/30/16 5:40 AM:
---------------------------------------------------------------
I have a customer that uses the NTLogEventAppender with Log4j 1. When we
migrate the product he uses to Log4j 2, I've got to have that in place.
I think we can have a log4j-windows module for this. Building this DLLs is easy
as long as you have the tools installed, probably not something we can in
Jenkins unless we have a Windows VM, but the Log4j 1 build also mention using
MingW instead of MS C.
In fact, I just built this log4j 1 DLL today with MS C for a x86 target env as
opposed to amd64, it takes 5 seconds.
was (Author: garydgregory):
I have a customer that uses the NTLogEventAppender with Log4j 1. When we
migrate the product he uses to Log4j 2, I've got to have that in place.
I think we can have a log4j-windows module for this. Building this DLLs is easy
as long as you have the tools installed, probably not something we can in
Jenkins unless we have a Windows VM, but log4j 1 build also mention using MingW
instead of MS C.
In fact, I just built this log4j 1 DLL today with MS C for a x86 target env as
opposed to amd64, it takes 5 seconds.
> 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]