Re: [log4net] [VOTE] migrate log4net from svn to git

Gregory wrote: +1, note that this kind of vote could be a "lazy" vote IMO. Gary On Apr 18, 2017 5:37 AM, "Dominik Psenner" <dpsen...@apache.org> wrote: This is a vote to migrate the source code of the log4net subproject from subversion over to git. [ ] +1, yes let's mig

Re: Discussion about logging on Reddit

Good Morning Chen Sad to see you leave. You can unsubscribe yourself by sending a mail to dev-unsubscr...@logging.apache.org. Cheers, Dominik On 2017-04-21 03:52, Chen Y wrote: Please remove me from this mailing list. Thank you On Apr 20, 2017 9:28 AM, "Mikael Ståldal"

[log4net] [Discuss] migration to git

Hi, As of today log4net is about one of the last logging subprojects that still uses svn and it makes sense to me that we migrate also this subproject over to git. What do you think? Cheers, Dominik

[log4net] [VOTE] migrate log4net from svn to git

This is a vote to migrate the source code of the log4net subproject from subversion over to git. [ ] +1, yes let's migrate to git [ ] 0, I don't care because... [ ] -1, don't migrate to git because... The vote will remain open for 72 hours at least. All votes are welcome and we encourage

Re: Log4net website issue

Stefan Bodewig wrote: On 2017-04-18, Dominik Psenner wrote: We probably should at least add a remark that points readers to the SDK reference and avoid the double effort of maintaining the documentation on the website too. Likely, in particular since we've broken it twice during the 2.0.x r

Re: Antwort: [Newsletter] Re: Log4net website issue

Regarding the consistency with other log4 projects, I as a .NET developer and log4net user, consider consistency with other .NET documentation (aka MSDN-Style) much more important then with let's say log4j. I don't think either that we should re-style the SDK reference. The issue we try to

Re: Chainsaw download links and release

The log4net jenkinsfile pipeline is complicated because it targets many different frameworks, each one requiring different conditional compiletime constants. This java application should be by far easier to build by targeting the smallest java version to be supported. I would certainly not expect

Re: Logger names for nested classes

es and potentially other languages. For example, in > > Scala, > > > an > > > > >> "object" class is a singleton instance of the class (vaguely > similar > > > to > > > > a > > > > >> c

Re: Logger names for nested classes

onfig using "A", it does not affect > A$N1 and A$N2 as you might expect, since "$" is not a ".". > > What about treating "$" like a "."? > > Thoughts? > > Gary > -- Dominik Psenner

Re: Logger names for nested classes

, configurations, .. Could a logger name attribute be an option? 2017-08-12 20:44 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > Hi, > > Why does that matter? > > Gary > > On Aug 12, 2017 12:34, "Dominik Psenner" <dpsen...@gmail.com> wrote: > > > Are t

Re: [jira] [Updated] (LOG4J2-2010) Allow customization of the conversion from logger names to logger hierarchy

classes), therefore I would like to know what the community thinks. Do you think this feature makes sense for log4net? 2017-08-14 10:29 GMT+02:00 Dominik Psenner (JIRA) <j...@apache.org>: > > [ https://issues.apache.org/jira/browse/LOG4

Re: [jira] [Updated] (LOG4J2-2010) Allow customization of the conversion from logger names to logger hierarchy

Please discuss whether we want to give the user the possibility to inject a custom implementation of a logger hierarchy calculation strategy. 2017-08-14 10:24 GMT+02:00 Dominik Psenner (JIRA) <j...@apache.org>: > > [ https://issues.apache.org/jira/browse/LOG4

Re: build.apache.org down

=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16087206 2017-07-16 18:17 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > FYI, the master node is offline but at the same time it is "in sync" and > has a latency of "0 ms". > > 2017-07-16 18:09 GMT+02:00 Dominik Psenner <d

Re: build.apache.org down

FYI, the master node is offline but at the same time it is "in sync" and has a latency of "0 ms". 2017-07-16 18:09 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > Hi, > > I just noticed that since midnight no builds are going through, probably > caus

Re: build.apache.org down

Ah, thanks! My fault that i missed the notification. :-) sorry for the noise. On 16 Jul 2017 6:33 p.m., "Stefan Bodewig" <bode...@apache.org> wrote: > On 2017-07-16, Dominik Psenner wrote: > > > I just noticed that since midnight no builds are going through, probabl

build.apache.org down

Hi, I just noticed that since midnight no builds are going through, probably caused by a large part of the build slaves that are offline. Has anyone of you received a notification for a maintenance downtime? See: https://builds.apache.org/computer/ Cheers -- Dominik Psenner

Re: [log4net] ci pipeline status update

GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > Hi, > > I finally managed to build the netstandard assemblies in our jenkins > pipeline. It was a tough task and the solution feels like a hack, but it > works. See: > > https://builds.apache.org/job/logging-log4net/j

Re: Build failed in Jenkins: log4net-trunk-tests #112

I broke the runtests target when I refactored the tests to make them run in the pipeline. This probably means that the test project fetches nunit framework with a different filename than it is shipped with the zip file we download. It was probably a bad idea to download the dependency manually. We

[log4net] ci pipeline status update

? log4net/netstandard/log4net.tests/log4net.tests.csproj Cheers -- Dominik Psenner

Re: [log4net] ci pipeline status update

2017-07-09 18:22 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-07-09, Dominik Psenner wrote: > > > I finally managed to build the netstandard assemblies in our jenkins > > pipeline. It was a tough task and the solution feels like a hack, but it >

Re: [log4net] ci pipeline status update

t is only present in the release assemblies. :-( -- Dominik Psenner

Re: [log4net] ci pipeline status update

: https://github.com/bdruemen/jenkins-docker-uid-from-volume/blob/master/Dockerfile On 9 Jul 2017 7:10 p.m., "Dominik Psenner" <dpsen...@gmail.com> wrote: > dotnet test inside of the directory is what I've done so far. >>> >>> Stefan >>> >> >> I

Re: [log4net] ci pipeline status update

Alternatives that may allow us to do the same are gosu and su-exec. Note that sudo won't work. On 10 Jul 2017 10:25 a.m., "Dominik Psenner" <dpsen...@gmail.com> wrote: > I just stumbled upon this which may allows us to detect the expected uid > that a docker container is

Re: [log4net] ci pipeline status update

inforation from there. Last but not least, we could patch and fix the dotnet cli tool to not require a valid user in the docker container... On 10 Jul 2017 10:33 a.m., "Stefan Bodewig" <bode...@apache.org> wrote: > On 2017-07-10, Dominik Psenner wrote: > > > I just stumbled u

[log4net] jenkins build fails with a stacktrace

-- Dominik Psenner

Re: [log4net] ci pipeline status update

:47 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > If this was not about hacking it would be a lot easier to accomplish.  > > I found also out that it is good practice to add arguments to the > dockerfile. This would then be the interface to pass in environment > variabl

Re: [log4net] ci pipeline status update

On 19 Jul 2017 6:35 a.m., "Stefan Bodewig" <bode...@apache.org> wrote: On 2017-07-18, Dominik Psenner wrote: > oohh how I like to be the bringer of good news! Right now I was finally > able to fix the building of the netstandard target by providing a > jenkinsfile sc

Re: [log4net] ci pipeline status update

that ReleaseInstructions is merely there as a source of information while we model the entire process in the cd-pipeline. Contributing already contains the information of how it should be in the future. Cheers, Dominik 2017-07-19 11:58 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > I hav

[log4net] attempt to fix the indentation chaos

quot; unexpand --first-only --tabs=$TABSIZE $FILE | sponge $FILE $ find -type f -name *.cs -exec unexpand-file {} \; Cheers -- Dominik Psenner

Re: [log4cxx] Release process releated questions

If xx&& is complicated why not ship a makefile with an install target? On 25 Jul 2017 9:16 a.m., "Thorsten Schöning" wrote: > Guten Tag Robert Middleton, > am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie: > > > As far as I'm aware, the configure.sh is not

Re: Opportunities for cohesion improvement and refatoring.

Hi, You should do atomar modifications in single commits and file one pull request for a sensible set of patches. Remember to also write sensible commit messages that explain what is done and why it is done. This allows easy and fast code reviews. Github is great for doing all but the actual

[log4net] set up basic multibranch and pull requests build

artifacts are not set up yet. Please review and let me know what you think of this. Cheers -- Dominik Psenner

Re: [log4net] set up basic multibranch and pull requests build

An idea crossed my mind. Couldn't we build the Mono binaries on the ubuntu machines? .net core should build both on ubuntu and on windows. nant is available also for ubuntu and a perfect candidate for a build tool. It would be even nicer if we could simply add mono as a dependency (i.e. nuget) and

Re: [log4net] pull request #11

Sounds like a plan that is fine with me given that this is just a minor change. 2017-07-01 18:22 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-06-30, Dominik Psenner wrote: > > > While working on the Jenkinsfile so that jjenkins builds all kinds of > > b

Re: [log4net] set up basic multibranch and pull requests build

GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > An idea crossed my mind. Couldn't we build the Mono binaries on the ubuntu > machines? .net core should build both on ubuntu and on windows. nant is > available also for ubuntu and a perfect candidate for a build tool. It > would b

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #44

[Pipeline] // stage > [Pipeline] stage > [Pipeline] { (build mono-3.5) > Stage 'build mono-3.5' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (build mono-4.0) > Stage 'build mono-4.0' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (build netstandard) > Stage 'build netstandard' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (build site) > Stage 'build site' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (prepare package) > Stage 'prepare package' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (publish site) > Stage 'publish site' skipped due to earlier failure(s) > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (Declarative: Post Actions) > [Pipeline] step > -- Dominik Psenner

[log4net] automated builds and some fresh air for the project

* run manual tests of the assemblies if they actually work * ... there is surely even more to do Step forward if you would like to get involved! :-) Cheers! -- Dominik Psenner

Re: Build failed in Jenkins: logging-log4net » feature/RollingFileAppender-NG #4

Looks like this is working too. Changes to the branch develop also causes merge requests against that branch to be merged and built. Thats great stuff to have, but also means that pull requests that stay open for long are going to fill our inboxes. What do you think? Should pull request builds

Fwd: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #72

// stage [Pipeline] stage [Pipeline] { (prepare package) Stage 'prepare package' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (check test results) Stage 'check test results' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (publish site) Stage 'publish site' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) -- Dominik Psenner

[log4net] test failure

est.TestExclusiveLockLocks () <0x41e7c150 + 0x002b7> in :0 -- Dominik Psenner

Re: Build failed in Jenkins: logging-log4net » feature/cd-pipeline #56

t; 76KUCPODUF6LCE45226EBUR4GNVLYPMYVC23Z4ITBOMNJT3CA2WA/tests/ > nant.build(29,3): > > Unable to download 'https://github.com/nunit/ > nunitv2/releases/download/2.6.4/NUnit-2.6.4.zip' to '/nunit.zip'. > > Access to the path "/nunit.zip" is denied. > > > > Total time: 1.4 seconds. > > > > [Pipeline] } > > $ docker stop --time=1 6bf59f2586bc7b22afb15e04f8c1d9 > 2a2ae5bd184f75843c457ca9e77d641c35 > > $ docker rm -f 6bf59f2586bc7b22afb15e04f8c1d9 > 2a2ae5bd184f75843c457ca9e77d641c35 > > [Pipeline] // withDockerContainer > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (build mono-3.5) > > Stage 'build mono-3.5' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (build mono-4.0) > > Stage 'build mono-4.0' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (build netstandard) > > Stage 'build netstandard' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (build site) > > Stage 'build site' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (prepare package) > > Stage 'prepare package' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (check test results) > > Stage 'check test results' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (publish site) > > Stage 'publish site' skipped due to earlier failure(s) > > [Pipeline] } > > [Pipeline] // stage > > [Pipeline] stage > > [Pipeline] { (Declarative: Post Actions) > > [Pipeline] step > -- Dominik Psenner

[log4net] git repository is online

Hi, I'm pleased to announce that the new git repository for the log4net subproject is up! It can be found here: https://git-wip-us.apache.org/repos/asf/logging-log4net.git github integration is enabled for this repository and therefore it is mirrored to github here:

Re: [log4net] git repository is online

I've just filed a ticket to INFRA to make the svn repository read-only: https://issues.apache.org/jira/browse/INFRA-14022 On 2017-04-27 09:28, Dominik Psenner wrote: Hi, I'm pleased to announce that the new git repository for the log4net subproject is up! It can be found here: https://git

[log4net] svn.a.o/r/a/logging/log4net/site

Hi, I just noticed that log4net has a html version of the website committed at svn as a sibling of trunk at [1]. Stefan, you did some commits there back in 2012. I assume that the content is obsolete and we don't mind if that content is not available on the git repository. Is this correct?

Re: [log4net] git repository is online

will just > confuse people. > > Ralph > > > On Apr 27, 2017, at 12:41 AM, Dominik Psenner <dpsen...@gmail.com> > wrote: > > > > I've just filed a ticket to INFRA to make the svn repository read-only: > > > > https://issues.apache.org/jira/browse/INFRA-1

Re: [log4net] git repository is online

What would you recommend to do with the pull requests? 2017-04-27 13:30 GMT+02:00 Apache <ralph.go...@dslextreme.com>: > I recommend that the git mirror of the sun repo be deleted. It will just > confuse people. > > Ralph > > > On Apr 27, 2017, at 12:41 AM, Dominik

Re: [log4net] git repository is online

Stefan has mastered all levels that exist for making jenkins configurations. :-) On 2017-04-28 17:05, Matt Sicker wrote: Can we? Most likely. Does anyone know how to configure it like that? 樂 On 28 April 2017 at 10:01, Dominik Psenner <dpsen...@gmail.com> wrote: When we see that j

Re: [log4net] git repository is online

On 2017-04-28 06:43, Stefan Bodewig wrote: Before svn goes read-only we may want to remove the contents of trunk and add a single README saying that we moved to git with pointers to the Apache repo as well as the new github mirror. I thought that adding a little information on the website

Re: [log4net] git repository is online

On 2017-04-28 11:04, Stefan Bodewig wrote: Not really. But we need to update the log4net website. I'll see to it later today. Great! I planned to do that this evening around 22:00 CET, but the kids are probably going to interfere with these plans. :-D We should probably hold back deleting

Re: Patch

and it makes our code look > professional. Thanks. > -- Dominik Psenner

Re: [log4net][log4php] Xml Config file

; On 7 August 2017 at 07:59, Dominik Psenner <dpsen...@gmail.com> wrote: > > > You have an application that both runs log4net AND log4php in the same > > process? > > > > On 7 Aug 2017 12:51 p.m., "Domínguez Moraleja, Jose Luis" < > > jldoming

Re: [log4net][log4php] Xml Config file

You have an application that both runs log4net AND log4php in the same process? On 7 Aug 2017 12:51 p.m., "Domínguez Moraleja, Jose Luis" < jldomingue...@sice.com> wrote: > I'm working in a project and we want to use this two libraries log4php and > log4net. > > We want to use just one

Re: Fwd: nant on debian stretch

s over at sourceforge. > > Hope this helps, > Ryan > > On Aug 18, 2017 8:44 AM, "Dominik Psenner" <dpsen...@apache.org> wrote: > > I just sent the following to the nant-developers mailing list. > > -- Forwarded message -- > From: Domin

Fwd: nant on debian stretch

I just sent the following to the nant-developers mailing list. -- Forwarded message -- From: Dominik Psenner <dpsen...@apache.org> Date: 2017-08-18 17:18 GMT+02:00 Subject: Fwd: nant on debian stretch To: nant-develop...@lists.sourceforge.net Hi there, I'm reaching out

Re: LOGCXX Jira Mail Setting

Hi Stefan, I think this is an administrative task that needs to be done by INFRA. While I can access the Administration page of the log4net jira project, I can't edit the notifications settings myself. Maybe this applies to logcxx too? {quote

Re: [LOG4NET] [VOTE] gitflow

I envision to automate the build and publishing process. At work we are migrating to git and along with that we are going to set up our (insane) build process with gitlab runners executed by virtualbox executors. See https://docs.gitlab.com/runner/ and

[log4net] jenkins

Hi Ralph, would you please grant me karma to add/modify log4net build configurations on jenkins? Warm regards -- Dominik Psenner

Re: [log4net] jenkins

Hi Stefan, Thanks and greetings! Cheers, Dominik On 2017-06-23 09:07, Stefan Bodewig wrote: Hi Dominik you should be set now, I've used my Gump PMC chairman powers and added you to the LDAP group for Jenkins admins. Stefan On 2017-06-22, Dominik Psenner wrote: *bump* I would still like

[LOG4NET] [VOTE] gitflow

. +1: Yes! +0: Go ahead, don't care that much. -0: Don't like it, but not vetoing it. -1: No, don't do that! I have a better idea! This vote follows the "lazy consensus" (no -1/vetoes). The vote will be open for at least 72 hours after that I'm going to push the develop branch. -- Dominik Psenner

Re: [1/2] logging-log4net git commit: This migrates the visual studio solution to Visual Studio 14

I'm a vi guy and have no need for a decent window manager. ;-) Can I proceed with bumping the solution to visual studio 2015 and removing all solution files on the master branch? 2017-05-22 18:19 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-05-22, Dominik Psen

Re: [Newsletter] Re: [LOG4NET] gitflow

oking for. They behave like "the" > > develop > > branch, but for supporting older version. > > The GitVersion Manual has some nice example images for this: > > http://gitversion.readthedocs.io/en/latest/git-branching- > > strategies/gitflow-examples/#sup

Re: [1/2] logging-log4net git commit: This migrates the visual studio solution to Visual Studio 14

I hoped to hear that. keeping 4 sln in sync is a major effort with no profit. Do we want lazy votes when an upgrade to a new vs version is immanent? On 21 May 2017 6:02 a.m., "Stefan Bodewig" wrote: > On 2017-05-19, wrote: > > > This migrates the visual

Re: [LOG4NET] gitflow

,..? These are the three kinds of branches I see at the moment. On 21 May 2017 6:11 a.m., "Stefan Bodewig" <bode...@apache.org> wrote: > On 2017-05-19, Dominik Psenner wrote: > > > would we like to use gitflow for our named branches? [1] > > I've used gitflow in one or two proje

Re: [1/2] logging-log4net git commit: This migrates the visual studio solution to Visual Studio 14

On 2017-05-22 13:59, Stefan Bodewig wrote: As long as we keep NAnt as the build tool of truth the solution files are "only" a convenience feature for people using VS (likely everybody except myself :-). How do you develop log4net if not with visual studio?

Re: [log4net] Remove log4net github repo?

On 25 May 2017 2:37 p.m., "Stefan Bodewig" <bode...@apache.org> wrote: I've asked infra to remove the repo: https://issues.apache.org/jira/browse/INFRA-14233 On 2017-05-25, Dominik Psenner wrote: > I have cloned the repository from [1] and fetched also all open pull > r

Re: [log4net] Remove log4net github repo?

2017-05-25 23:09 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > While applying the pull requests I stumbled upon pr/22 which is based on > the branch log4net-1.2.x. That branch has a lot of modifications but I am > unsure whether or not those changes have been merged into trunk or

Re: [LOG4NET] gitflow

t; So ATM for example in HttpComponents' HttpCore we have a 4.4.x and master > branch that are BOTH going to be used for releases. > > How do you deal with that in Gitflow? > > Gary > > On Fri, May 19, 2017 at 1:10 PM, Dominik Psenner <dpsen...@gmail.com> > w

Re: [LOG4NET] gitflow

expected. :-) 2017-05-19 23:26 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > If I understand the usecase correctly, then there should be these branches: > > * master > * release/4.4.1.x > * release/4.4.2.x > > Note that there could be even more branches if "u

[LOG4NET] gitflow

Hi, would we like to use gitflow for our named branches? [1] [1] https://datasift.github.io/gitflow/IntroducingGitFlow.html Cheers -- Dominik Psenner

[logging-log4net] Git Push Summary

Hi, I just did a fresh clone of the log4net repository and noticed that this head had appeared in the git repository. I don't know where it came from but it looks like it was an artifact that was still there because of the svn -> git migration. The parents of this commit looked to me like a

Re: [log4net] [jira] issue notifications

gt; gets mirrored to JIRA which means sometimes I'll get 3 or 4 emails of the > same message! > > On 8 June 2017 at 10:44, Dominik Psenner <dpsen...@apache.org> wrote: > >> Hi, >> >> currently jira sends issue notifications to: >> >> * all watchers >

[log4net] [jira] issue notifications

Hi, currently jira sends issue notifications to: * all watchers * current assignee * reporter * single email address (dev@l.a.o) This puts two mails into my inbox on issues that I've picked up. Given that possible assignees are (and should anyway) all be subscribed to dev@l.a.o I would like

Re: [GitHub] logging-log4net issue #3: Support for types of non-parameterless constructor...

Thanks for sharing your idea. Property and ctor initialization should work together as it does in c#. Properties are set on the object that was initialized by calling the ctor. If ctor directives are missing in the xml config, the empty would be used. Similarily, an empty ctor xml config is

[log4net] [jira] [vote] remove "current assignee" from issue notifications

Hi, As a follow up to this discussion I'm starting a vote to remove the "current assignee" from the list of notifications in the LOG4NET jira project. This will reduce the number of duplicate mails if one has both assigned an issue and is subscribed to the dev list. +1: Yes! -1: No, don't

Re: [LOG4NET] [VOTE] gitflow

Hi, On 2017-05-23 08:49, Stefan Bodewig wrote: Please ensure github tracks develop as the default branch when the vote passes. I just filed an issue on INFRA to make this happen. This is the ticket for it: https://issues.apache.org/jira/browse/INFRA-14316 Cheers, Dominik

Re: [LOG4NET] [VOTE] gitflow

cause then it > > matches > > > the terminology of most git documentation and tutorials on the web). > > > > > > > > > Sorry, drive by email. I've been subscribed this email list for a > > decade > > > but I don't think I've ever posted before. > > > > &g

Re: The Apache Software Foundation Welcomes 64 New Members

Thanks Stefan! I'm glad to have become part of the family and look forward to a journey that is going to last for long. On 2017-05-04 11:48, Stefan Bodewig wrote: On 2017-05-04, Mikael Ståldal wrote: Congratulations Matt! Yes, congrats to Matt and Dominik. Stefan

Re: [log4net] rel/tags

I'm happy to let you know that I've finished rewriting the rc tags. The tags look well organized now. 2017-05-24 18:43 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > > > On 24 May 2017 6:09 p.m., "Stefan Bodewig" <bode...@apache.org> wrote: > >

Re: Moving log4net-logviewer to apache

On 2017-09-18 07:16, Ralph Goers wrote: https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327423060 and the following comment sounds as if "moving to Apache" was seen as a way to keep logviewer maintained. I'm not convinced this would be any easier here than in github so

Re: [jira] [Resolved] (INFRA-14645) node requirements for jenkins job logging-log4net

August 2017 at 23:32, Dominik Psenner <dpsen...@gmail.com> wrote: Hi, Chris just resolved our infra ticket regarding .net frameworks on the windows nodes. This is a summary of the outcome: Chris Thistlethwaite resolved INFRA-14645. -- Resolution: Fi

Re: Moving log4net-logviewer to apache

Hi Oskar, log4net-logviewer is a tool that includes both a command line and a ui frontend written in wpf/xaml that both can parse logfiles and provide users a better view on log events. According to the readme this is a alternative to log2console and chainsaw. I don't like it to have

Re: Moving log4net-logviewer to apache

to be able to comment on this. Would you please explain the main difference between chainsaw, log2console and log4net-logviewer? Best regards from Oskar On 6 Sep 2017, at 13:54, Dominik Psenner <dpsen...@gmail.com> wrote: Hi Oskar, log4net-logviewer is a tool that includes both a comman

Re: [GitHub] logging-log4net issue #13: Support combination of roll by size, preserve fil...

The implementation of the RollingFileAppender uses the IDateTime interface to get the current datetime. You can mock that interface. On 2017-09-13 14:20, EbenZhang wrote: Github user EbenZhang commented on the issue: https://github.com/apache/logging-log4net/pull/13 >What about

Re: [jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

I opt that everyone should use the library in a way that makes sure deadlocks cannot happen. Trying to solve this by fancy "deadlock could occur" mechanisms feels wrong. A very restrictive mode of operation could enforce that all arguments passed into a log event must be limited to immutable

Re: [jira] [Commented] (LOG4J2-2031) Messages appear out of order in log file (was: Log4j2 log file not reflecting application log function calls)

:06 p.m., "Dominik Psenner" <dpsen...@gmail.com> wrote: > I opt that everyone should use the library in a way that makes sure > deadlocks cannot happen. Trying to solve this by fancy "deadlock could > occur" mechanisms feels wrong. > > A very restrictive

Re: [jira] [Commented] (LOG4NET-552) Incorrect behavior of RollingFileAppender while rolling files, if multiple processes appending into same file

On 21 Aug 2017 10:37 a.m., "Sachin Abaso Patil (JIRA)" wrote: [ https://issues.apache.org/jira/browse/LOG4NET-552?page= com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel=16134885#comment-16134885 ] Sachin Abaso Patil commented on LOG4NET-552:

Re: Logger names for nested classes

>>> > >>>> It seems the sane thing to do to: > >>> > >>>> - Avoid making something pluggable in log4j-api > >>> > >>>> - Avoid making Core parse logger names looking for separators. > >>> > >>>> > >>> > >>> > >>> > >>> But that would mean adding two methods to: > >>> > >>> > >>> > >>> org.apache.logging.log4j.spi.LoggerContext: > >>> > >>> > >>> > >>> org.apache.logging.log4j.spi.LoggerContext.getLogger(Class) > >>> > >>> org.apache.logging.log4j.spi.LoggerContext.getLogger(Class, > >>> > >>> MessageFactory) > >>> > >>> > >>> > >>> Thoughts? > >>> > >>> > >>> > >> > >>> > >> Why does it mean that? > >>> > >> > >>> > > > >>> > > If we want the core to implement converting Class names to Logger > >>> names, > >>> > > the Class must be passed down to the Core. Right now the LogManager > >>> does > >>> > > that by calling org.apache.logging.log4j.spi.LoggerContext > methods. > >>> > These > >>> > > methods take only String for the logger name. > >>> > > >>> > And that is a problem because….? I am trying to understand why > >>> > LoggerContext will be required to accept a class name. > >>> > > >>> > Ralph > >>> > > >>> > > >>> > >>> > >>> -- > >>> Matt Sicker <boa...@gmail.com> > >>> > >> > >> > > > -- Dominik Psenner

Fwd: [jira] [Resolved] (INFRA-14645) node requirements for jenkins job logging-log4net

Hi, Chris just resolved our infra ticket regarding .net frameworks on the windows nodes. This is a summary of the outcome: > Chris Thistlethwaite resolved INFRA-14645. > -- >Resolution: Fixed >> 1. We have observed that none of the windows nodes

Re: Logging list for emails generated by tools

he > >>> extra emails and I have a hard time filtering this list because of how > >> some > >>> of the emails are generated. > >>> > >>> I would also say that we expect every committer to be subscribed to > that > >>> list. > >>> > >>> Ralph > >>> > >> > > > > > > > > -- > > Matt Sicker <boa...@gmail.com> > > > -- Dominik Psenner

log4net on gcloud

. Quoting the disclaimer: > Find and fix your production issues > Track the health of your app once it’s running in production with Stackdriver Logging via the popular .NET log4net library. Cheers and greetings -- Dominik Psenner [1] https://cloud.google.com/dotnet/ [2] https://cloud.goog

lognet license file

-- Dominik Psenner

Re: [NuGet Gallery] Message for owners of the package 'log4net'

log4net package references that are not upgraded for > netcoreapp 2.0. Please, would you mind to upgrade them? > > Thanks in advance. Best regards, > > Borja > > > -- Dominik Psenner

Re: Async Appenders

When implementing the async/await paradigm it would have to be provided as a logging event api and continuously invoked with async down to the appender implementations in order for the application code to benefit from true async behavior. Or am I wrong here? On 2018-05-09 13:48, William

Re: Async Appenders

ync/await uses. To be completely > > lock-free, an alternative wait strategy is to busy-spin but this means > > dedicating a core to logging which is a hefty price. In the disruptor > this > > is configurable so if log4j users really want to they can have lock-free > > logging in return fo

Re: Async Appenders

Java. :) > > On 9 May 2018 at 13:09, Dominik Psenner <dpsen...@gmail.com> wrote: > > > Disclaimer: so far I never had to use a library like LMAX disruptor. > After > > a lot of brain that I spent into the new async/await approach that's > > available today I even

Re: Async Appenders

k io which also explains more in-depth details of how it works: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/ As a starting point it surely takes time to grasp and caused me some headache. :-) 2018-05-09 20:33 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>:

Re: Async Appenders

ike locks and notifications since those are implemented via threads, > and > > > fibers don't get their own execution context like threads do (hence why > > > they're much faster where applicable due to less context switching and > > data > > > copying need

Re: Async Appenders

tack > seems to be getting lots of logs :) I'll reach out to Nick at SE and see if > he can expound upon his previous message. > > On Thu, May 10, 2018 at 5:55 PM, Dominik Psenner <dpsen...@gmail.com> > wrote: > > > Interesting discussion in that pull request, yet i

Re: Async Appenders

+1 :-) I only have very limited time frames available to hack on log4net but am happy to help wherever help is needed. For instance we have to fix the build pipeline to have something to rely on and allow contributions to be sanity checked by tests. On 8 May 2018 5:05 p.m., "Matt Sicker"

Re: [log4net] dotnet test host process crashes or hangs when run by jenkins docker container

Psenner <dpsen...@gmail.com>: > *bump* > > Has anyone out there an idea how we could troubleshoot the issue or any > ideas what else we could do? > > > > On 2018-02-03 11:51, Dominik Psenner wrote: > >> The first message was rejected by the mailing list, please s

  1   2   3   4   5   6   7   8   9   10   >