Guys,
LOG4NET-393 is causing us some problems at $work. It's fixed as of 1.3.0, which
doesn't appear to be released yet. Is there an expected date for it to be
released, and if not what can I do to help make this happen?
And while I have your attention, I noticed that we released the log4net
On 2013-11-06, Nick Williams wrote:
LOG4NET-393 is causing us some problems at $work. It's fixed as of
1.3.0, which doesn't appear to be released yet. Is there an expected
date for it to be released, and if not what can I do to help make this
happen?
If you need anything fast, then it is
[
https://issues.apache.org/jira/browse/LOG4NET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-391:
---
Issue Type: Improvement (was: Bug)
XmlLayoutSchemaLog4j does permit logging without
On 2013-11-06, Dominik Psenner wrote:
Since LOG4NET-393 is a blocker for people who work a lot with lambda
expressions and right now we have absolutely no idea as of when 1.3 will be
ready we might better release 1.2.13 containing the fix for the issue.
Yeah, no problem with that, I'll try to
[
https://issues.apache.org/jira/browse/LOG4NET-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-394:
---
Fix Version/s: (was: 1.3.0)
1.2.13
Lambda-based ILog-Extensions
[
https://issues.apache.org/jira/browse/LOG4NET-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-393:
Assignee: Stefan Bodewig (was: Dominik Psenner)
Using dynamic methods with log4net
[
https://issues.apache.org/jira/browse/LOG4NET-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-393.
Resolution: Fixed
Fix Version/s: (was: 1.3.0)
1.2.13
And while I have your attention, I noticed that we released the
log4net NuGet package for 1.2.10 as 1.2.10, but 1.2.11 and 1.2.12
were 2.0.0 and 2.0.1, respectively. 1.2.12 was then re-released as
2.0.2. Since I've only been with Apache Logging since the spring and
I'm completely new to
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
2013/11/6 Stefan Bodewig bode...@apache.org
On 2013-11-06, Dominik Psenner wrote:
Since LOG4NET-393 is a blocker for people who work a lot with lambda
expressions and right now we have absolutely no idea as
Ideally there would be two different packages for the strong name and the
new name, but this has to be discussed with the package maintainer.
2013/11/6 Joe jocular...@hotmail.com
And while I have your attention, I noticed that we released the
log4net NuGet package for 1.2.10 as 1.2.10, but
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see anything
you feel fits and we'll go from
On 2013-11-06, Dominik Psenner wrote:
Maybe we can craft some other small and easy fixes that we can ship with
1.2.13.
Oh, even though I've already tagged the sources in svn don't let that
hold you back, tags are cheap. Look through JIRA if you see anything
you feel fits and we'll go from
12 matches
Mail list logo
