NN created LOG4NET-480:
--
Summary: Fix lo4net testst run
Key: LOG4NET-480
URL: https://issues.apache.org/jira/browse/LOG4NET-480
Project: Log4net
Issue Type: Bug
Components: Builds
Affects
[
https://issues.apache.org/jira/browse/LOG4NET-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NN updated LOG4NET-482:
---
Attachment: LOG4NET-482.patch
> ILog Format methods with exception
> --
>
>
NN created LOG4NET-482:
--
Summary: ILog Format methods with exception
Key: LOG4NET-482
URL: https://issues.apache.org/jira/browse/LOG4NET-482
Project: Log4net
Issue Type: Improvement
Affects
[
https://issues.apache.org/jira/browse/LOG4NET-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NN updated LOG4NET-482:
---
Flags: Patch
> ILog Format methods with exception
> --
>
> Key:
[
https://issues.apache.org/jira/browse/LOG4NET-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NN updated LOG4NET-481:
---
Affects Version/s: 1.2.12
Description:
All tests of RemotingFileAppender fail.
Tests also have
NN created LOG4NET-478:
--
Summary: TPL for .NET 3.5
Key: LOG4NET-478
URL: https://issues.apache.org/jira/browse/LOG4NET-478
Project: Log4net
Issue Type: Improvement
Components: Appenders
How could we at compile time know if TPL is available at runtime through
third party libraries? We would have to ship yet another slightly
differently compiled library for .net 3.5 and I dont like that fact. Other
opinions welcome.
On 25 Oct 2015 7:45 a.m., "NN (JIRA)" wrote:
>
NN created LOG4NET-479:
--
Summary: Cannot compile log4net.vs2008
Key: LOG4NET-479
URL: https://issues.apache.org/jira/browse/LOG4NET-479
Project: Log4net
Issue Type: Bug
Components: Builds
NN created LOG4NET-481:
--
Summary: RemotingFileAppenderTest fails
Key: LOG4NET-481
URL: https://issues.apache.org/jira/browse/LOG4NET-481
Project: Log4net
Issue Type: Bug
Affects Versions: 1.2.13,
[
https://issues.apache.org/jira/browse/LOG4NET-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NN updated LOG4NET-482:
---
Remaining Estimate: 1h
Original Estimate: 1h
> ILog Format methods with exception
>
[
https://issues.apache.org/jira/browse/LOG4NET-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-479.
Resolution: Fixed
Fix Version/s: (was: 1.2.14)
1.2.15
patch
[
https://issues.apache.org/jira/browse/LOG4NET-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-483.
Resolution: Won't Fix
allow applications to depend on 1.3 and 1.2 at the same time (one of
[
https://issues.apache.org/jira/browse/LOG4NET-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973767#comment-14973767
]
NN commented on LOG4NET-483:
I see.
How I join the mailing list?
Thanks
> Assembly name for log4net 1.3 is
NN created LOG4NET-483:
--
Summary: Assembly name for log4net 1.3 is log4net-1.3.dll and not
log4net.dll
Key: LOG4NET-483
URL: https://issues.apache.org/jira/browse/LOG4NET-483
Project: Log4net
Issue
14 matches
Mail list logo