Hi all,
this is just a random list, I'd like to make sure whether we are on the
same page before making changes or just give the user list a heads up.
My understanding of the discussion which basically happened in JIRA so
far:
* the next release will be 1.3.0 and require .NET 2.0 or better
[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791283#comment-13791283
]
Stefan Bodewig commented on LOG4NET-383:
LOG4NET-318 maybe?
Log4Net.Error
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790367#comment-13790367
]
Stefan Bodewig commented on LOG4NET-397:
http://svn.apache.org/viewvc/logging
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789058#comment-13789058
]
Stefan Bodewig commented on LOG4NET-397:
Joe, you are right. When we considered
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789062#comment-13789062
]
Stefan Bodewig commented on LOG4NET-397:
type forwarding wouldn't work for 1.x
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789079#comment-13789079
]
Stefan Bodewig commented on LOG4NET-397:
So far I had assumed you had
Hi all,
not sure whether I find an audience big enough or whether we need to
expand this to the user list.
One option to get out of the oldkey/newkey problems mentioned in
https://issues.apache.org/jira/browse/LOG4NET-397 would be to make the
move to a log4net2 assembly.
The short term plan
On 2013-10-08, Dominik Psenner wrote:
1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
not mind breaking backwards compatibility within 1.X even further. The next
good milestone could be 1.3 RC1 since we won't be compatible with log4j2 and
we should go to 2.X only if
On 2013-10-04, Stefan Bodewig wrote:
I've contacted cincura.net via the NuGet website and hope to hear
back. It would be great to have her/him on board addressing the
packaging related issues and maybe help streamline the process of
publishing future packages.
Never heard back
On 2013-10-08, Dominik Psenner wrote:
Never heard back, but with
http://blog.cincura.net/233419-log4net-nuget-package-updated-without-
some-goodies/
and https://github.com/cincuranet/log4net-nuget we could simply point
people to github and close all Nuget related issues immediately.
+1
[
https://issues.apache.org/jira/browse/LOG4NET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789236#comment-13789236
]
Stefan Bodewig commented on LOG4NET-358:
see also
http://blog.cincura.net/233419
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-392:
---
Labels: nuget patch (was: patch)
Updating causing Config issue
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-392:
---
Component/s: (was: Builds)
Updating causing Config issue
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-392.
Resolution: Won't Fix
we'd like to see this fixed but can't fix it as the Nuget package
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-392:
sorry, I can't seem to change the resolution without re-opening the issue.
Mark, you
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-395.
Resolution: Won't Fix
invalid is not a proper resolution for an existing bug we just
[
https://issues.apache.org/jira/browse/LOG4NET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-358:
Visual Studio snippet within the deployment with NuGet
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-395:
Nuget packaging problem - Creates app.config file in ALL projects when
applying package
On 2013-10-04, Dominik Psenner wrote:
Recently the noise about NuGet packages became louder and the time has come
talk about this. We know of two open issues that have to be addressed by the
owner of the NuGet package distribution:
https://issues.apache.org/jira/browse/LOG4NET-395
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783055#comment-13783055
]
Stefan Bodewig commented on LOG4NET-392:
we don't build/provide NuGet packages
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783118#comment-13783118
]
Stefan Bodewig commented on LOG4NET-392:
I've contacted the NuGet package's owner
[
https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777542#comment-13777542
]
Stefan Bodewig commented on LOG4NET-232:
.NET 4.0 is available for XP, so
[
https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777552#comment-13777552
]
Stefan Bodewig commented on LOG4NET-232:
In that case my VM won't help as it runs
[
https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777996#comment-13777996
]
Stefan Bodewig commented on LOG4NET-232:
no need to be sorry. And thank you
Hi all,
even though 72 hours are not up, I've aleady copied the zips to the
distribution area to give the mirrors a head-start. Right now a commit
for the website is underway as well.
Unless a -1 shows up I'll make flip the switch on the website and send
out vote result and announce mails in a
On 2013-09-12, Stefan Bodewig wrote:
even though 72 hours are not up, I've aleady copied the zips to the
distribution area to give the mirrors a head-start. Right now a commit
for the website is underway as well.
If you go to http://logging.apache.org/log4net/log4net-1.2.12/ you can
see
With three +1 by Dominik, Christian and myself and no other votes the
release has been accepted.
I've already copied the distribution archives and will now proceed with
the rest of the release process. I'll change the site to reflect the
new release immediately but will hold off sending out the
On 2013-09-12, Dominik Psenner wrote:
Now that the SDK reference is on logging.apache.org the page encoding is
broken again. There's something fishy going there. See this screenshot:
Ouch.
The main difference is one svn commit/checkout cycle.
I think svn expects files to have an UTF-8
the release.
For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:
http://logging.apache.org/log4net/
Stefan Bodewig on behalf of the log4net community
-BEGIN PGP SIGNATURE-
Version
Hi all,
after about two years it's more than about time to cut a new release.
log4net 1.2.12 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/logging/log4net
(revision 2850)
Details of changes since 1.2.11 are in the release notes:
http://people.apache.org/~bodewig
On 2013-09-09, Dominik Psenner wrote:
I'm not checking the source changes but only website stuff etc. At a first
glance I found these issues on the web page:
* the download page is broken
I should have said so. Yes, this is to be expected as I must not run
CGIs from my homedir.
* the SDK
I forgot to explicitly add my own +1 to the release.
On 2013-09-09, Dominik Psenner wrote:
A minor gotcha I can see (on ubuntu at the moment) is, that the SDK TOC
on the left is only a few pixels high where it should probably use the
entire vertical space:
Maybe it's just a
On 2013-09-06, Dominik Psenner wrote:
And yet another month went past and I've got to apologize for being unable
to test this so far on another machine. However, since this is no regression
from 1.2.11 and the tests fail only for me and I was unable to find out
what's actually going on on
On 2013-09-02, ramprasad.sayana wrote:
I am using log4net dll in my project
Am able to write to a file successfully.
Problem is...If I run my exe parallelly, logging from second exe is
stopped until first exe's execution is completed.
On 2013-08-14, Dominik Psenner wrote:
2013/8/14 Stefan Bodewig bode...@apache.org
The application runs for 3 days and thus log4net rolls the logfile 3
times.
Well, I live in a world where all log files of an application are kept
inside the same folder :-)
For me too, but I've seen enough
You've looked into this far more than I have but do your really feel the
persistent storage is needed? To me scenarios like I have manually
deleted some log files or I have reconfigured the rolling conditions
don't really have to be supported by our rolling logic. If people
interfere with
On 2013-08-13, d_k wrote:
Whats wrong with rolling on logging events?
For one we have JIRA issues that say something is wrong :-)
OK, as long as your application logs frequently, there is no problem.
But if you have a policy that rolls on date boundaries and your
application tends to be idle
On 2013-08-12, Dominik Psenner wrote:
The log filename should be determined dynamically to allow users including
information like %date, %time in the filename. It has often been requested
and up to now it is supported only marginally.
+1
Another issue that I just remembered now is that
[just changing the subject :-)]
On 2013-08-12, Dominik Psenner wrote:
Yesterday it became quite late and I had not the mental force to write down
my vision of the RFA reimplementation:
The log filename should be determined dynamically to allow users including
information like %date, %time
On 2013-08-09, Dominik Psenner wrote:
I've just re-run the tests and all RemotingAppenderTest are failing. I've
digged how stacktraces are exchanged in remoted events so that might have
broken something. :-(
Strange, they pass for me.
Anyway, I'll hold back building the release to give you
On 2013-08-09, Dominik Psenner wrote:
It may be related to some of those new and fancy security restrictions
introduced with Win7. On which windows do you run the tests, Stefan?
XP, otherwise I'd be unable to create the .NET 1.x builds.
Stefan
On 2013-08-09, Dominik Psenner wrote:
Do you have the possibility to try the tests on a win7?
Not without quite a bit of effort (i.e. obtaining an Apache MSDN
subscription and installing win7 in the first place :-).
You may want to check out the svn tag of log4net 1.2.11 and see whether
the
Hi,
I now think I have a build environment (again) that allows me to cut a
release. One thing I noticed is that the same XP VM I used to build the
1.2.11 release from no longer wants to build the Compact Framework 2.x
binaries. One of the software updates of the past two years must have
On 2013-08-08, Dominik Psenner wrote:
There is:
I've just run the tests and the RemotingAppenderTests seem to fail. Until
now I don't know why. Ideas?
Line 103? Yes, fails for me as well. I'll look into it later, can't
promise to come up with an idea, though :-)
I get two more test errors
I've cheated and disabled the tests again for now :-)
On 2013-08-03, Dominik Psenner wrote:
Whether it builds cleanly or not doesn't actually matter. We can fix the
errors when the build system builds our targets. When the tests are run too
it seems to be complete.
I've just enabled the tests, they'll probably run on .NET 4.0.
Just before that
On 2013-08-05, Apache Jenkins Server wrote:
See https://builds.apache.org/job/log4net-trunk-build/4/changes
this fails because NUnit isn't found.
I vaguely recall I had to copy the nunit framework DLL to the test's bin
directory to make things work but haven't touched my build setup in such
a
On 2013-08-01, Dominik Psenner wrote:
The last few lines indicate a windows 7 security related issue with
nant.
Yes, I know, I've already told our infra guys.
I've run into this a few time
Same here:
http://stefan.samaflost.de/blog/en/Apache/Log4Net/working_on_the_1.2.11_release.html
:-)
On 2013-03-06, Dominik Psenner wrote:
Now that we are talking about superhuman power. Stefan, are you still
out there somewhere? ;-)
The honest answer probably is barely. I keep hoping to find time to
get more involved again.
As for nightly builds. I don't think you want to build the full
On 2012-11-28, Dominik Psenner wrote:
*hm* .. using maven 2.2.1 it seems to work flawlessly. At least it does not
produce warnings. ;-) I checked the site and mostly only the dates are
changed now. *yay!*
[Sorry for being almost totally absent, and not only here. Currently I
have no idea
Dear log4net community,
it is my pleasure to inform you, Dominik has been elected as a new
committer to the project. He's been active around here for quite some
time and will now be able to work on the code base directly. I'm sure
the project is going to benefit a lot from him.
Welcome Dominik
On 2012-06-08, Dominik Psenner wrote:
In response to
https://issues.apache.org/jira/browse/LOG4NET-344?focusedCommentId=13291557
I would like to start a discussion how log4net should support
asynchronous logging. Tom Tang implemented a general async forwarding
appender that glues together
On 2012-06-08, Christian Grobmeier wrote:
Hi,
On Fri, Jun 8, 2012 at 8:39 AM, Dominik Psenner dpsen...@gmail.com wrote:
* the ThreadPool should be used in favour over a designated worker Thread
no idea becuase I have no clue on .NET, but it sounds like fun :-)
.Net has a built-in thread
[
https://issues.apache.org/jira/browse/LOG4NET-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288474#comment-13288474
]
Stefan Bodewig commented on LOG4NET-344:
Many thanks Tom!
Either you have
On 2012-04-11, Ron Grabowski wrote:
The converter is trying to protect itself...the base class checks to
make sure HttpContext.Current is not null then a check against Request
is made:
Sounds like checking the property throws an exception. Its probably ok
to just add in a try/catch and
[
https://issues.apache.org/jira/browse/LOG4NET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-331.
Resolution: Fixed
Fix Version/s: 1.2.12
fixed with svn revision 1345626
[
https://issues.apache.org/jira/browse/LOG4NET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288099#comment-13288099
]
Stefan Bodewig commented on LOG4NET-330:
My first guess is your mail appender
[
https://issues.apache.org/jira/browse/LOG4NET-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-328.
Resolution: Invalid
user question, not an issue
Log4Net for Windows
[
https://issues.apache.org/jira/browse/LOG4NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-320:
why has this issue been resolved?
Location Information
[
https://issues.apache.org/jira/browse/LOG4NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288110#comment-13288110
]
Stefan Bodewig commented on LOG4NET-320:
Relocating the code sounds good to me
[
https://issues.apache.org/jira/browse/LOG4NET-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288113#comment-13288113
]
Stefan Bodewig commented on LOG4NET-321:
Yes, I think this could be modelled like
[
https://issues.apache.org/jira/browse/LOG4NET-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288114#comment-13288114
]
Stefan Bodewig commented on LOG4NET-325:
IIUC you don't want the pattern
[
https://issues.apache.org/jira/browse/LOG4NET-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288115#comment-13288115
]
Stefan Bodewig commented on LOG4NET-326:
I agree this could be useful, we'd
[
https://issues.apache.org/jira/browse/LOG4NET-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288118#comment-13288118
]
Stefan Bodewig commented on LOG4NET-329:
FileAppender's Encoding property
Hi all,
we currently create the online API docs via the ancient NDoc and HTML
Help compiler combo. When I put together the 1.2.11 release I was lucky
enough to use a machine that had been in use for a long time and so had
all the required pieces installed.
Now my dev environment is a freshly
[
https://issues.apache.org/jira/browse/LOG4NET-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288122#comment-13288122
]
Stefan Bodewig commented on LOG4NET-336:
Not easy to write a testcase
Hi,
[CCing you since I'm not sure you are subscribed to the list]
I've made a port of log4net to MonoDroid (Mono for Android).
This really looks interesting. Can you tell us a little bit about it -
I must admit I'm a total ignorant when it comes to MonoDroid.
Have you faced any major
[
https://issues.apache.org/jira/browse/LOG4NET-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-343.
Resolution: Fixed
Fix Version/s: 1.2.12
Assignee: Stefan Bodewig
[
https://issues.apache.org/jira/browse/LOG4NET-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288011#comment-13288011
]
Stefan Bodewig commented on LOG4NET-340:
I'll immediately agree with Dominilk
[
https://issues.apache.org/jira/browse/LOG4NET-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-333.
Resolution: Won't Fix
Simon is right, we did have releases that have broken binary
[
https://issues.apache.org/jira/browse/LOG4NET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253980#comment-13253980
]
Stefan Bodewig commented on LOG4NET-233:
trunk should work without any
[
https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248077#comment-13248077
]
Stefan Bodewig edited comment on LOG4NET-27 at 4/6/12 5:32 AM
[
https://issues.apache.org/jira/browse/LOG4NET-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13248085#comment-13248085
]
Stefan Bodewig commented on LOG4NET-27:
---
One problem I see is that the file added 26
[
https://issues.apache.org/jira/browse/LOG4NET-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-322.
Resolution: Fixed
Fix Version/s: 1.2.12
Thanks!
Patch applied in svn revision
On 2012-01-13, Ron Grabowski wrote:
Anyone know why there are extended chars in most of the log4net ndoc
files? For example this page has empty-blocks in IE9 and
triangle-question-marks in Firefox:
No idea, I used the existing ndoc target in the NAnt build file that I
assume has been used for
On 2011-12-23, Ramon Smits wrote:
I can share some thought about this new key philosophy regarding they
anyone should be able to patch it but I think it is wrong. How can I
validate a package from untrusted sources if they have access to the
'official' private key ?
The only official binary
[
https://issues.apache.org/jira/browse/LOG4NET-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164287#comment-13164287
]
Stefan Bodewig commented on LOG4NET-319:
There shouldn't be any dependency
[
https://issues.apache.org/jira/browse/LOG4NET-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164407#comment-13164407
]
Stefan Bodewig commented on LOG4NET-319:
All DLLs are inside the binary
[
https://issues.apache.org/jira/browse/LOG4NET-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164410#comment-13164410
]
Stefan Bodewig commented on LOG4NET-316:
I agree with the SDK docs.
The site
[
https://issues.apache.org/jira/browse/LOG4NET-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164461#comment-13164461
]
Stefan Bodewig commented on LOG4NET-105:
I know its been five years ...
I think
[
https://issues.apache.org/jira/browse/LOG4NET-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-283.
Resolution: Fixed
Fix Version/s: (was: 1.2 Maintenance Release
[
https://issues.apache.org/jira/browse/LOG4NET-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13163584#comment-13163584
]
Stefan Bodewig commented on LOG4NET-316:
What would be your personal choice
[
https://issues.apache.org/jira/browse/LOG4NET-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-316:
---
Fix Version/s: 1.2.12
Code is in as svn revision 1210987
I've added a tiny test that shows
[
https://issues.apache.org/jira/browse/LOG4NET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13160964#comment-13160964
]
Stefan Bodewig commented on LOG4NET-233:
Igor, are you sure you are using
[
https://issues.apache.org/jira/browse/LOG4NET-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13160968#comment-13160968
]
Stefan Bodewig edited comment on LOG4NET-318 at 12/1/11 4:26 PM
[
https://issues.apache.org/jira/browse/LOG4NET-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-260:
---
Fix Version/s: (was: 1.2 Maintenance Release)
difference filter and object render
[
https://issues.apache.org/jira/browse/LOG4NET-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-222:
---
Fix Version/s: (was: 1.2 Maintenance Release)
1.2.12
[PATCH
[
https://issues.apache.org/jira/browse/LOG4NET-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13158534#comment-13158534
]
Stefan Bodewig commented on LOG4NET-233:
NN, which defines do you think are wrong
[
https://issues.apache.org/jira/browse/LOG4NET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-292.
Resolution: Fixed
Thanks!
Patch applied as svn revision 1203145
[
https://issues.apache.org/jira/browse/LOG4NET-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-227:
---
Component/s: (was: Builds)
Appenders
create a more directory when
[
https://issues.apache.org/jira/browse/LOG4NET-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145577#comment-13145577
]
Stefan Bodewig commented on LOG4NET-227:
rollingStyle of Composite means you
[
https://issues.apache.org/jira/browse/LOG4NET-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-202:
---
Affects Version/s: 1.2.11
Fix Version/s: (was: 1.2 Maintenance Release
[
https://issues.apache.org/jira/browse/LOG4NET-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-292:
---
Affects Version/s: (was: 1.2.10)
1.2.11
Fix Version/s
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4net has an issue affecting its community integration.
This
[
https://issues.apache.org/jira/browse/LOG4NET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13139547#comment-13139547
]
Stefan Bodewig commented on LOG4NET-254:
I'm not aware of any log4net specific
[
https://issues.apache.org/jira/browse/LOG4NET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13139547#comment-13139547
]
Stefan Bodewig edited comment on LOG4NET-254 at 10/30/11 6:19 AM
[
https://issues.apache.org/jira/browse/LOG4NET-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138161#comment-13138161
]
Stefan Bodewig commented on LOG4NET-246:
Thanks Uri. No, I think all is done now
[
https://issues.apache.org/jira/browse/LOG4NET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-315:
---
Fix Version/s: (was: 1.2 Maintenance Release)
1.2.12
[
https://issues.apache.org/jira/browse/LOG4NET-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13136060#comment-13136060
]
Stefan Bodewig commented on LOG4NET-315:
Can't the server argument
[
https://issues.apache.org/jira/browse/LOG4NET-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127416#comment-13127416
]
Stefan Bodewig commented on LOG4NET-178:
Can you check whether the problem still
501 - 600 of 895 matches
Mail list logo
