[ 
https://issues.apache.org/jira/browse/LOG4NET-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375066#comment-15375066
 ] 

ASF GitHub Bot commented on LOG4NET-467:
----------------------------------------

Github user jasonwilliams200OK commented on the issue:

    https://github.com/apache/log4net/pull/16
  
    > @arkadiuszwojcik the goal of this PR is to make log4net portable across 
.NET Core platforms. Implementing those abstractions could be useful, but doing 
so wouldn't enable consuming log4net on additional platforms.
    
    I agree and I think that can be a separate repo / package, something like 
log4net.Extensions.Logging. However, having this Extensions package first hand 
from original vendor (Apache) is vital on multiple accounts.
    
    ---
    
    Separately, can this PR get some prio love from the reviews please? All the 
providers listed here: https://github.com/aspnet/Logging#providers, are not as 
popular as log4net and we (folks running stuff on dotnet core) hoping to get 
our hands on apache/log4net bits.
    
    @chlowell, could you please prepare a SVN patch for the reviewers? We can 
always have subsequent PRs to refine stuff. If you are aiming to add CI setup 
for .NET Core TxM as part of this PR, feel free to grab Travis/AppVeyor bits 
from https://github.com/autofac/Autofac.Extras.Moq/pull/6/files.


> Is .NET Core, will be supported in the near future, or not
> ----------------------------------------------------------
>
>                 Key: LOG4NET-467
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-467
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.13
>            Reporter: san kan
>              Labels: features
>
> As you know, ms is moving heavily toward .Net core:
> https://github.com/dotnet/core
> so, is there a road map for making a version that supports it?
> and i noticed that log4net, has not been updated for 2 years.
> so is it maintained, or being forgotten?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to