Re: String Equality Comparison, Broken Tests and .NET-1.x

On 2016-08-22, wrote: > A recent commit [1] changed, among other things, some string equality > comparisons from `SomeComparer.Compare(a, "B", IgnoreCase) == 0` to > `a.ToUpperInvariant() == "B"`, see also [2]. > > Unfortunately, this doesn't work if `a` is allowed to be null. Currently a > lot o

Apache log4net Needs Help

have come and gone when their interests or just the amount of time they could invest have changed. At the moment Dominik Psenner and Stefan Bodewig are the only people semi-actively working on log4net and neither of them is able to devote as much time to the project as they'd like to and as wou

Re: Apache log4net Needs Help

On 2016-09-06, Gert Driesen wrote: > I've got my hands full at the moment, but I'll try to step up and contribute > to log4net on a best effort basis. Would be good to have you back. Cheers Stefan

Re: String Equality Comparison, Broken Tests and .NET-1.x

Hi Jonas On 2016-08-23, wrote: > Stefan Bodewig wrote on 23.08.2016 06:14:32: >> On 2016-08-22, wrote: >>> Should we create some helper in SystemInfo that provides null-aware, >>> ordinal, casing-agnostic string equality comparison, with some #if's >>

Re: Fix for FileAppender's TextWriter creation in OpenFile

On 2016-08-22, wrote: > `FileAppender` has a vritual overload for the Method `SetQWForFiles` that > takes a `Stream` and creates a StreamWriter from it. According to the API > documentation > """ > This method can be overridden by sub classes that want to wrap the > in some way, for example to e

Re: Happy to help

Hi Jim On 2016-09-08, Jim Christopher wrote: > I hear log4net needs some help. I'm happy to offer what time I can. this is great. > Please point me at something you'd like me to tackle. The log4net JIRA holds a lot of open tickets. Maybe something looks interesting to you. Right now I use th

Version Number

Hi right now the "traditional" log4net assemblies of the next release would be 1.2.16. The next nuget package would be 2.0.6 and the .NET Core project creates 3.0.0. I'm confused by this. :-) I'm not sure we need to allign all three versions but some consistence would be good. Any preferences?

Re: Happy to help

On 2016-09-09, Ryan Boggs wrote: > On Sep 8, 2016 9:23 PM, "Stefan Bodewig" wrote: >> It feels like this is only a short term solution as NAnt is becoming >> more of an obstacle than help by not supporting recent frameworks >> anymore. So I expect we'll st

Re: Version Number

On 2016-09-09, Dominik Psenner wrote: > There are quite a few options and the decision is interleaved with the > infrastructure of hacking/build environment. Depending on how we deal > with the different target frameworks in the future it might be wise to > align versioning numbers along with the

Building .NET Core Version (was Re: Version Number)

On 2016-09-09, Dominik Psenner wrote: > Would that work with nant? How does one compile a library that works > on .net core anyway? Is there an extension for visual studio that adds > a target framework? As I don't use VS I don't know about this myself. The .NET Core SDK comes with a "dotnet" CL

NAnt and Mono (was Re: Happy to help)

On 2016-09-09, Ryan Boggs wrote: > Fyi - One thing i do know regarding NAnt, mono, and windows is that when > they updated the installer for 4, they omitted the registry settings for > the first couple of releases so NAnt couldn't find it. I went back to 3.12.1 after your comment but NAnt 0.92 st

netstandard version of the .NET Core build

Hi right now the .NET Core build builds for netstandard1.3. Why 1.3? Reading https://github.com/dotnet/corefx/blob/master/Documentation/architecture/net-platform-standard.md my impression is we could use netstandard 1.0 up to 1.6 and it wouldn't make any difference for people using the .NET Core

Re: netstandard version of the .NET Core build

On 2016-09-11, Gert Driesen wrote: > I suppose it's 1.3 because 1.0 has an even more limited API surface. > A lot of CoreFX packages are not available for netstandard 1.0. > For SSH.NET - an OSS project I spend most of my time on right now - I also > chose 1.3 because of this. Thanks, this explai

Re: NAnt and Mono (was Re: Happy to help)

On 2016-09-11, Ryan Boggs wrote: > On Sep 11, 2016 2:23 AM, "Stefan Bodewig" wrote: >> On 2016-09-09, Ryan Boggs wrote: >>> Fyi - One thing i do know regarding NAnt, mono, and windows is that when >>> they updated the installer for 4, they omitted the regis

Re: NAnt and Mono (was Re: Happy to help)

On 2016-09-11, Ryan Boggs wrote: > On Sep 11, 2016 9:21 AM, "Stefan Bodewig" wrote: >> On 2016-09-11, Ryan Boggs wrote: >>> On Sep 11, 2016 2:23 AM, "Stefan Bodewig" wrote: >>>> On 2016-09-09, Ryan Boggs wrote: >>>>> Fyi - One

Re: NAnt and Mono (was Re: Happy to help)

On 2016-09-12, Ryan Boggs wrote: > On Sep 12, 2016 1:43 AM, "Stefan Bodewig" wrote: >> It looks as if System.dll now resides in mono/4.0-api rather than >> mono/4.0 (the later only holds Mono.Posix.dll and mscorlib.dll). > Ok, initial glance tells me that this could

Things to do before the next release

Hi all right now I'm able to build .NET 2.0 up to 4.5 and .NET Core with a single invocation of NAnt on my Win7 VM. We'll see if I find a way to also include Mono there, alternatively I can - once again - jiggle with two different machines and use an older version of Mono on Linux. This is I volun

Informational Version (was Re: Things to do before the next release)

On 2016-09-14, Stefan Bodewig wrote: > * decide on the version. I propose to use 2.0.6.0 for the next release > for all artifacts and try getting the "informational version" right - > this is Dominik's second proposal in > https://l

Re: Informational Version (was Re: Things to do before the next release)

a build or more verbose information that usually doesnt fit > into the version numbering scheme. > https://msdn.microsoft.com/en-us/library/system.reflection.assemblyinformationalversionattribute(v=vs.110).aspx > On 2016-09-14 17:24, Stefan Bodewig wrote: >> On 2016-09-14, Stef

Re: Informational Version (was Re: Things to do before the next release)

On 2016-09-14, Stefan Bodewig wrote: > so we could simply suppress the warning. done. Stefan

Documentation Update for .NET Core

Hi all, I've added minimal content for the upcoming release, a build of the site is at . The download link is deliberately broken, you can see the expected HTML content at .

Test-Builds for log4net 2.0.6

Hi all I've created files from trunk that could be close to the next release and uploaded them to http://stefan.samaflost.de/staging/log4net-2.0.6/ This is not a release, but I'd ask people to give them a try as I don't expect us to change much before the real 2.0.6 release. It looks as if I for

Re: Test-Builds for log4net 2.0.6

On 2016-09-30, Dominik Psenner wrote: > I've just checked the zip archives and found that within the archive > there is a net-cp folder. Shouldn't that read as net-cf for compact > framework? cp == client profile. We don't provide CF binaries at all with 2.0.6. Stefan

Has anybody found time to test the 2.0.6 test builds?

Hi all as the subject says. I'd really like to cut the 2.0.6 release soonish but without anybody testing what we currently have this may just end up in a useless exercise of the release process. Stefan

Re: Has anybody found time to test the 2.0.6 test builds?

On 2016-10-12, Dominik Psenner wrote: > Time flies and as always spare time is rare. There is once a lot of work > related stuff to do and I cant swim fast enough to reach the shore. Please > give me more time. Oh, I fully understand that, we are in the same boat most of the time. Take your time.

Re: deploy beta version to nuget.org

On 2016-10-06, Raymond Sanchez wrote: > I went to nuget.org and I don't see a beta version for log4net for the > current work. > If we have a beta version, more developers can get involved with testing > the latest version. At the ASF even a beta release is a release which requires a vote. One

Re: [GitHub] log4net issue #25: API to flush appenders that buffer logging data

On 2016-10-12, Dominik Psenner wrote: > The patch looks sensible. Whats your opinion stefan? all the whitespace changes are distracting. And the patch contains changes that are completely unrelated - it seems to contain pull request #24 as well. I'll comment on the PR. Stefan

2.0.6 test build available via myget

Hi all I've set up a personal account at myget and published my test build there: https://www.myget.org/feed/log4net-test/package/nuget/log4net Maybe this lowers the bar for testing. Please note this is a developer snapshot and in no way an official release of log4net. The myget feed is not mean

Re: Response to call to arms

On 2016-10-18, Joe wrote: > I'm responding to Stefan's call-to-arms, though I have limited time > available, currently probably not more than a day or two a month. Which may be more than Dominik and I have spent in some month. Welcome! > Given my lack of time I would probably want to get involve

Re: Response to call to arms

Welcome Tommy I'm sure we can use your expertise if we'd want to handle our platform zoo in an easier way :-) Also, since you mention .NET Core. I've created some test builds[1] as precursor for the next release - this was before we started to merge Joe's pull requests. AFAIK nobody has verified

Re: Should an Appender be IDisposable?

On 2016-10-21, Joe wrote: > I think the answer is probably yes: a FileAppender owns an IDisposable > Stream, and other appenders probably own IDisposable objects. Probably. Likely this has been overlooked when log4net was started. > I would suggest having AppenderSkeleton implement IDisposable,

Re: Better support for logging from an Appender

On 2016-10-21, Joe wrote: > From within DoAppend, there is a flag m_recursiveGuard which should > prevent re-entrancy problems from a synchronous appender's Append > method. For an asynchronous appender there would need to be an > additional check since it will want to log from a different thread

Re: AsyncAppenderSkeleton

On 2016-11-03, Joe wrote: > However I don’t understand your point about event formatters – are > there any formatters that aren’t thread safe? It doesn’t seem to be > an unreasonable restriction to require writers of formatters / layout > implementations to be thread-safe. It may not be unreason

Re: Apache log4net Needs Help

On 2016-11-05, Joe wrote: >> If you are willing to help, please join log4net's dev mailing list and raise >> your hand. Look through log4net's issue tracker and pick things you'd like >> to work on. If you don't know where to start, please ask, Dominik and Stefan >> will be there to help. >> I

Towards 2.0.6

Hi all I'd like to get 2.0.6 released in order to help out people who want to use log4net with .NET Core. We've had some changes since I built the last test assemblies, but AFAIK nobody has given them a try anyway. I wonder whether creating test assemblies is worth the effort or whether I should

Re: Towards 2.0.6

"Joe" wrote: > I just had a quick look through the commits since 1.2.15 and I don't see > anything that looks particularly risky. > I'd vote for cutting an RC. > -Original Message- > From: Stefan Bodewig [mailto:bode...@apache.org] > Sent: 06 Nove

Re: Towards 2.0.6

On 2016-11-07, Dominik Psenner wrote: > LOG4NET-487 is about the configuration option and the issue I would > like to see in the release. The reason is, not having this > configurable costs performance and creating a mutex always is > troublesome to some configurations. I should be able to carve

Re: Towards 2.0.6

On 2016-11-07, Dominik Psenner wrote: > LOG4NET-487 is about the configuration option and the issue I would > like to see in the release. The reason is, not having this > configurable costs performance and creating a mutex always is > troublesome to some configurations. The latter resulted in > LO

[VOTE] Release log4net 2.0.6 based on RC1

Hi all log4net 2.0.6 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/logging/log4net (revision 17495) Details of changes since 1.2.15 are in the release notes: http://stefan.samaflost.de/staging/log4net-2.0.6/release/release-notes.html I have tested this with Mono

Re: [VOTE] Release log4net 2.0.6 based on RC1

On 2016-12-22, Dominik Psenner wrote: > thanks for carving out 2.0.6. I'm looking through the website and am > going to run some sanity checks right now. Are you planning to push > this to nuget? Once the release vote has passed, yes. Stefan

Re: [VOTE] Release log4net 2.0.6 based on RC1

On 2016-12-22, Dominik Psenner wrote: > A question about the .net core support: > according to the documentation, .net remoting is not available with > .net standard 1.3. Would that mean too that the > log4net.ThreadLogicalContext is not available either because it > requires System.Runtime.Remot

Re: [VOTE] Release log4net 2.0.6 based on RC1

s is inside the appendix about how anybody can apply the license to their own work (which wouldn't be copyright by the ASF and probably use different years from log4net). See also http://www.apache.org/licenses/LICENSE-2.0 Stefan > On 2016-12-20 11:07, Stefan Bodewig wrote: >> Hi

Re: [VOTE] Release log4net 2.0.6 based on RC1

Making my own vote explicit On 2016-12-20, Stefan Bodewig wrote: > Votes, please. This vote will close in 72 hours, 1000 GMT 24-Dec 2016 > [X] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... +1 Stefan

Re: [VOTE] Release log4net 2.0.6 based on RC1

Many thanks for reviewing On 2016-12-22, Gary Gregory wrote: > Running build.cmd succeeds. ASC, MD5, SHA1, SHA256 OK. If you are going to > provide SHA1 or SHA256, you can do away with MD5 IMO. > -1 based on the RAT check failures: > 18 Unknown Licenses most of them are generated, namely > b

[RESULT] Release log4net 2.0.6 based on RC1

The vote for Apache log4net 2.0.6 has passed with three binding +1s by Domink Psenner, Remko Popma and myself and one -1 by Gary Greggory. I'll now proceed with publishing the artifacts and will send out the release announcement once the mirrors have had time to catch up. Many thanks to those who

[ANN] Apache log4net 2.0.6 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Apache log4net team is pleased to announce the release of Apache log4net 2.0.6. The release is available for download at https://logging.apache.org/log4net/download_log4net.cgi as well as via nuget https://www.nuget.org/packages

[VOTE] Release log4net 2.0.7 based on RC1

Hi all this RC really only changes the nuget packaging and is - apart from the version number and the copyright line (happy new year) - identical to 2.0.6. log4net 2.0.7 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/logging/log4net (revision 17647) Details of chang

[RESULT] Release log4net 2.0.7 based on RC1

Hi all the vote has passed with binding +1s by Remko Popma, Dominik Psenner, Matt Sicker and myself (implicit). I'll publish the artifacts and wait for the mirrors to catch up before sending the announcement. Thanks to all who took the time to review the release Stefan

[ANN] Apache log4net 2.0.8 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Apache log4net team is pleased to announce the release of Apache log4net 2.0.7. The release is available for download at https://logging.apache.org/log4net/download_log4net.cgi as well as via nuget https://www.nuget.org/packages

[ANN] Apache log4net 2.0.7 Released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [Re-Sending with corrected subject] The Apache log4net team is pleased to announce the release of Apache log4net 2.0.7. The release is available for download at https://logging.apache.org/log4net/download_log4net.cgi as well as via nuget

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

[jira] [Issue Comment Deleted] (LOG4NET-435) Port log4net to Xamarin Android and Xamarin iOS targets

[ https://issues.apache.org/jira/browse/LOG4NET-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-435: --- Comment: was deleted (was: Delivery to the following recipient failed permanently

<    1   2   3   4   5   6   7   8   9   10   >