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: [Log4j] Release in README.md

OK, that works too. On 2017-09-18 06:07, Ralph Goers wrote: I am replacing the section in the README regarding Maven and Gradle with a link to the relevant web site page. Ralph On Sep 17, 2017, at 8:24 PM, Ralph Goers wrote: I have an issue with anything that references a release version i

Jenkins build is back to normal : Log4j 2.x #3081

See

Build failed in Jenkins: Log4j 2.x #3080

See Changes: [rgoers] Rename pom so release plugin will ignore it [rgoers] Comment out dependency for now -- [...truncated 4.66 MB...] [JENKINS] Archiving

Re: Moving log4net-logviewer to apache

> On Sep 17, 2017, at 9:47 PM, Stefan Bodewig wrote: > > On 2017-09-09, Dominik Psenner wrote: > >> What does the community think should happen? Are there people out there who >> use log4net-logviewer or any of its binaries? > > I don't. > > https://github.com/wallymathieu/log4net-logviewer/i

Re: Moving log4net-logviewer to apache

On 2017-09-09, Dominik Psenner wrote: > What does the community think should happen? Are there people out there who > use log4net-logviewer or any of its binaries? I don't. https://github.com/wallymathieu/log4net-logviewer/issues/7#issuecomment-327423060 and the following comment sounds as if "m

Re: [Log4j] Release in README.md

I am replacing the section in the README regarding Maven and Gradle with a link to the relevant web site page. Ralph > On Sep 17, 2017, at 8:24 PM, Ralph Goers wrote: > > I have an issue with anything that references a release version in the > README. Keeping that up to date requires that it

Re: [Log4j] Release in README.md

I have an issue with anything that references a release version in the README. Keeping that up to date requires that it manually be updated before the release to the release version and then be updated again after the release to the snapshot version. Everywhere else a version appears in things t

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169468#comment-16169468 ] Remko Popma commented on LOG4J2-2052: - I would prefer to keep the default as is, and

[jira] [Commented] (LOG4J2-2052) Disable thread name caching by default

[ https://issues.apache.org/jira/browse/LOG4J2-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169415#comment-16169415 ] Dan Berindei commented on LOG4J2-2052: -- Sure, I'm fine with changing it only on 8u10

Re: Chainsaw

Since Scott is telling people to download the source, build it and use it I would feel safe in saying it is production ready. However, I would take a look at the web site and see if anything there needs to be updated. Ralph > On Sep 17, 2017, at 12:00 PM, Matt Sicker wrote: > > If Scott can p

Re: Chainsaw

Depending on the state of the project, I might be interested in doing some development to add support for directly consuming Log4j 2's JsonLayout (using the parser support recently added to log4j-core). But I'll wait with that until after one proper release has been done. On 2017-09-17 21:00,

Re: Chainsaw

If Scott can polish up whatever needs to be done before a release, I can help coordinate the release itself. I'm not too familiar with the project, so I wouldn't know if it's release-ready or not beforehand, though. On 14 September 2017 at 19:46, Ralph Goers wrote: > Chainsaw has been in limbo f