[
https://issues.apache.org/jira/browse/LOG4NET-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651431#comment-16651431
]
Dominik Psenner commented on LOG4NET-613:
-----------------------------------------
What do you mean with component? An extension is typically an assembly (dll)
that is referenced in the application and configuration file. This means that
the extension codebase consists of at least a csproj file and a class that
implements the functionality. That codebase could live in the core repository.
In that case the build scripts would trigger the build and test the resulting
artifacts. Adding the codebase can be achieved with a pull request. Since the
contribution appears to be significant, you will have ti sign and file an ICLA
as well.
> Adding JSON serialization layout
> --------------------------------
>
> Key: LOG4NET-613
> URL: https://issues.apache.org/jira/browse/LOG4NET-613
> Project: Log4net
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.8
> Reporter: Jo Cutajar
> Priority: Minor
> Fix For: 2.1.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Hi,
> I've created an extension which will effectively enable Json logging from
> log4net. It is implemented as a Layout so it can be used with pretty much any
> appender, especially the UDP appender :o). The aim is to enable fast local
> UDP drop off for logs in combination with nxlog. But I took care to allow
> code reuse and flexibility.
> Project: [https://gitlab.com/BrightOpen/log4net.Ext.Json]
> Please help me [integrate this into
> log4net|https://gitlab.com/BrightOpen/log4net.Ext.Json/issues/1].
> Thanks, Jo
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
