[
https://issues.apache.org/jira/browse/LOG4NET-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-2:
-
Fix Version/s: (was: v.Next)
1.2.10
Configurator should report errors
[
https://issues.apache.org/jira/browse/LOG4NET-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-200:
Nothing has been changed in svn for this issue and there still are reports that
indicate the
[
https://issues.apache.org/jira/browse/LOG4NET-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-200:
---
Fix Version/s: (was: v.Next)
1.2 Maintenance Release
sounds as if
[
https://issues.apache.org/jira/browse/LOG4NET-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-229:
---
Fix Version/s: (was: v.Next)
1.2.11
Japanese characters get garbled
[
https://issues.apache.org/jira/browse/LOG4NET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-1:
-
Fix Version/s: (was: v.Next)
1.2 Maintenance Release
Support Fallback
[
https://issues.apache.org/jira/browse/LOG4NET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-176:
---
Fix Version/s: (was: v.Next)
1.2.11
Solution and project files went
[
https://issues.apache.org/jira/browse/LOG4NET-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-263:
---
Affects Version/s: (was: v.Next)
add event before write to log to cancel or continue
[
https://issues.apache.org/jira/browse/LOG4NET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-254:
---
Affects Version/s: (was: v.Next)
[PATCH] Added Snmp V1 Trap Appender
[
https://issues.apache.org/jira/browse/LOG4NET-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-226:
---
Affects Version/s: (was: v.Next)
Fix Version/s: 1.2 Maintenance Release
Allow
[
https://issues.apache.org/jira/browse/LOG4NET-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-110:
---
Affects Version/s: (was: v.Next)
[PATCH] Expand environment variables in filenames of
[
https://issues.apache.org/jira/browse/LOG4NET-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-94:
--
Fix Version/s: 1.2.11
Incorrect config file for ..\examples\net\1.0\Tutorials\ConsoleApp
[
https://issues.apache.org/jira/browse/LOG4NET-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-98:
--
Due Date: 01/Nov/06 (was: 01/Nov/06)
Affects Version/s: (was: v.Next)
[
https://issues.apache.org/jira/browse/LOG4NET-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-105:
---
Affects Version/s: (was: 1.2.11)
(was: v.Next)
[
https://issues.apache.org/jira/browse/LOG4NET-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-94:
--
Affects Version/s: (was: 1.2.11)
(was: v.Next)
Incorrect
[
https://issues.apache.org/jira/browse/LOG4NET-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-61:
--
Affects Version/s: (was: v.Next)
I need a Appender for Microsoft Message Queue (MSMQ)
[
https://issues.apache.org/jira/browse/LOG4NET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-174.
Resolution: Duplicate
Not strictly a duplicate and came in earlier than LOG4NET-233 but
[
https://issues.apache.org/jira/browse/LOG4NET-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13087638#comment-13087638
]
Stefan Bodewig edited comment on LOG4NET-174 at 8/19/11 10:44 AM:
[
https://issues.apache.org/jira/browse/LOG4NET-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-270.
Resolution: Fixed
Apart from the assembly title (which is part of LOG4NET-233 as well)
[
https://issues.apache.org/jira/browse/LOG4NET-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-271.
Resolution: Fixed
Patch is part of svn revision 1159487
[Patch] Bump trunk version to
[
https://issues.apache.org/jira/browse/LOG4NET-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-304.
Resolution: Duplicate
Not strictly a duplicate of LOG4NET-233 but we only need one issue
Author: bodewig
Date: Fri Aug 19 12:04:03 2011
New Revision: 1159605
URL: http://svn.apache.org/viewvc?rev=1159605view=rev
Log:
log4net enetered incubation in 2004
Modified:
logging/log4net/trunk/NOTICE
While, this is certainly a problem, it SHOULD not be the issue already
reported, because those reports were against log4Net running on the 2.0
CLR instead of the 4.0 CLR.
I have done some research this morning, and have found a couple of
articles suggesting fixes, but I do not yet understand the
On 2011-08-19, Roy Chastain wrote:
While, this is certainly a problem, it SHOULD not be the issue already
reported, because those reports were against log4Net running on the 2.0
CLR instead of the 4.0 CLR.
OK.
I have done some research this morning, and have found a couple of
articles
In answer to the question about the express editions being able to
target different framework levels and profiles.
I just found this statement
In Express Editions of Visual Studio, a .NET Framework version or
profile cannot be specified when a project is created. However, you can
later retarget
On 2011-08-19, Roy Chastain wrote:
I have done some research this morning, and have found a couple of
articles suggesting fixes, but I do not yet understand the
ramifications. This is all to do with a new code security model created
in 4.0 and it is going to take time to understand.
If
On 2011-08-19, Roy Chastain wrote:
I just found this statement
In Express Editions of Visual Studio, a .NET Framework version or
profile cannot be specified when a project is created. However, you can
later retarget the project to any installed .NET Framework version.
At
[
https://issues.apache.org/jira/browse/LOG4NET-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13088042#comment-13088042
]
Nicklas Norling commented on LOG4NET-176:
-
No it's not important. It's just
Author: bodewig
Date: Sat Aug 20 04:55:17 2011
New Revision: 1159844
URL: http://svn.apache.org/viewvc?rev=1159844view=rev
Log:
first attempt at building client profile assemblies
Modified:
logging/log4net/trunk/log4net.build
logging/log4net/trunk/log4net.include
Author: bodewig
Date: Sat Aug 20 05:22:22 2011
New Revision: 1159849
URL: http://svn.apache.org/viewvc?rev=1159849view=rev
Log:
brand management
Modified:
logging/log4net/trunk/src/AssemblyInfo.cs
logging/log4net/trunk/src/AssemblyVersionInfo.cpp
29 matches
Mail list logo
