Re: [VOTE] Move Chainsaw to dormant

+1 Thanks Christian Scott On 2/12/24, Christian Grobmeier wrote: > Hello, > > This vote is to put Chainsaw to the "Dormant" components. There is much work > to be done on this component, but not enough hours can be committed to do > that work. To reflect this situation to the user, it is

Re: [chainsaw] Status change?

Thank you for spending time working on it Christian. I started contributing to Chainsaw in 2003. I agree. It's time. The primary benefit of Chainsaw was its built-in support for real-time tailing of ssh-accessible pattern-layout based logs - something Kibana doesn't support well, and something

Re: [chainsaw] Question: oading/writing settings of ChainsawTabbedPane

That's great! Global app settings used to be loaded on startup and saved on exit. LogPanel-specific settings were persisted on exit and loaded on startup on a per-tab-name basis, mostly using LogPanelpreferenceModel. There are a few preferences I'd like to restore - the tab-expression event

Re: [chainsaw] Next steps? Or is it over?

I'll go through the UI and re-add small features that I think are critical but were lost in the log4j1-jettison effort. I'll follow-up in a new thread. Scott On 11/28/23, Scott Deboy wrote: > I've fixed the logger tree split pane UI (left artifacts when you > drag), and I've

Re: [chainsaw] Next steps? Or is it over?

ott, > > I believe you; thanks for speaking up and being around. > > How can I help? > > I think Chainsaw needs to see a release soon, so what can I do to help you? > > I am glad to clean up things and whatever is necessary. > > Kind regards, > Christian > > O

Re: [chainsaw] Next steps? Or is it over?

I have dropped the ball here, but will commit to working on this, this year. I want to preserve a bunch of what can be done in the https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep branch, and some of that just isn't possible because equivalent functionality was never added

Re: [chainsaw] What is necessary for a 2.2 release?

l programming/flow-based view would be very cool but also very > complicated. > > -Robert Middleton > > On Mon, Oct 9, 2023 at 3:24 PM Christian Grobmeier > wrote: >> >> On Sun, Oct 8, 2023, at 23:19, Scott Deboy wrote: >> > I started but haven't had much time

Re: [chainsaw] What is necessary for a 2.2 release?

toring properties. > > I am not sure what the status currently is, if Scott is still working on > it :) I could also make some kind of proposal or so for storing properties > > On Tue, Oct 3, 2023, at 01:20, Scott Deboy wrote: > > I think persisting to json format makes sen

Re: [chainsaw] What is necessary for a 2.2 release?

>> I didn't remove those things yet, as they seemed to big and I >> >>>>> didn't >> >>>>> understand well how they'd work or how I would test (I lack the >> >>> knowledge >> >>>>> of how the UI should operate but only see what is there

Re: [chainsaw] What is necessary for a 2.2 release?

easy to track): >>> >>> https://github.com/apache/logging-chainsaw/commit/75bedf98665188eef4d13e4bfbb4b0dae456f65e >>> >>> One question: why did we remove Xstream? it seem there was an update >>> late >>> 2022 to address some security. >>> Should we just re-enable it

Re: [chainsaw] What is necessary for a 2.2 release?

I pushed branch "chainsaw-with-log4j1-dep" representing the working log4j1 code for those that want to easily see what used to exist. I'll probably selectively incorporate pieces from that branch into master. On 10/1/23, Christian Grobmeier wrote: > > On Sun, Oct 1, 2023, at 21

Re: [chainsaw] What is necessary for a 2.2 release?

2023 at 3:14 PM Christian Grobmeier > wrote: > >> On Sun, Oct 1, 2023, at 20:59, Scott Deboy wrote: >> > It's great to see the contribution, thanks Christian! >> > >> > I pulled down latest master and it looks like there are some UI >> > glit

Re: [chainsaw] What is necessary for a 2.2 release?

On 10/1/23, Scott Deboy wrote: > It's great to see the contribution, thanks Christian! > > I pulled down latest master and it looks like there are some UI > glitches we should fix - for example, resizing the logger tree pane > doesn't render correctly. > > As I menti

Re: [chainsaw] What is necessary for a 2.2 release?

It's great to see the contribution, thanks Christian! I pulled down latest master and it looks like there are some UI glitches we should fix - for example, resizing the logger tree pane doesn't render correctly. As I mentioned before, I assume there are a bunch of features we lost when we moved

Re: Refining product feature set strategy

+1 to everything Ralph said. On Fri, Sep 29, 2023, 3:53 PM Ralph Goers wrote: > I’m sorry, I can’t really agree with much of any of this. Following the > thoughts being proposed in this thread much of Log4j 2 and even the initial > work I did to create it would not have seen the light of day.

Re: [chainsaw] Lots of commented code // Backwards compatibility?

I think Robert commented out most of that to get rid of the log4j1 dependency. I'm slightly concerned we'll lose a ton of UI functionality in that process, but it's in history if it's still needed, so delete away if you'd like. For comparison, you can look at the 'chainsaw-with-log4j1-dep'

Re: [chainsaw] Is ZeroConf support relevant?

This is a log4j2 feature. Scott On Fri, Sep 29, 2023, 12:24 PM Christian Grobmeier wrote: > Volkan asked this question here: > https://github.com/apache/logging-chainsaw/issues/24 > > I guess, since Log4j1 is EOL we can safely remove this feature, right? >

Re: [chainsaw] Trouble starting it at all

There should be a default config. Do you have anything in the .chainsaw directory? If so, delete it. On Fri, Sep 29, 2023, 9:49 AM Christian Grobmeier wrote: > OK, got it running, after commenting those lines: > > //statusBar.setSelected(config.getBoolean("statusBar")); >

Re: [Chainsaw] Thoughts on moving forward

by default. The UI supports multiple tabs (log sources) and will live tail for you as well. Note the search results show up as blue in the log panel, and the gutter on the right displays the individual line colors (black is a search match). On Mon, Sep 25, 2023 at 8:46 PM Scott Deboy wrote

Re: [Chainsaw] Thoughts on moving forward

nd it can better scroll like a > real terminal when new messages come in. Right-clicking will open up a > pop-up menu contextually depending on what it is you have clicked on(the > time, logger name, level, or the message). > > Anyway, that's what I personally feel would be mor

Re: [Chainsaw] Thoughts on moving forward

Please review the various display setting controls. Most of what you mention can be toggled from visible to hidden. VfsLogFilePatternReceiver does exactly what you're describing. Allowing live remote tailing of logs over an ssh accessible path. You control if these logs end up in separate tabs

Re: [VOTE] Move Chainsaw to dormant status

/ > > -Robert Middleton > > On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy > wrote: > > > -1 > > > > While changes may be infrequent, the project is still useful and works > > well. I'll continue to contribute to maintenance. > > > > Scott >

Re: [VOTE] Move Chainsaw to dormant status

-1 While changes may be infrequent, the project is still useful and works well. I'll continue to contribute to maintenance. Scott On Thu, Sep 21, 2023, 10:00 AM Volkan Yazıcı wrote: > As earlier discussions[1] indicate, Chainsaw has been lacking on > maintenance and no PMC member stepped up

Re: Retire Chainsaw

they can build a project that passes all their > security scans. > > Ralph > > > On Sep 19, 2023, at 11:26 AM, Scott Deboy wrote: > > > > Ralph, > > > > I already removed the socket appender vulnerability. I believe that was > the > > only one

Re: Retire Chainsaw

itHub Issues for Chainsaw AFAIK. > Both of these need to be addressed if the project is going to be considered > active. Are you willing to help with both of these? > > Ralph > > > On Sep 19, 2023, at 3:25 AM, Scott Deboy wrote: > > > > Well, it still works we

Re: Retire Chainsaw

Well, it still works well, and real time log analysis and Chainsaw's support for filtering are very powerful for many dev-local use cases. User base I can't speak to, but I agree based on lack of questions it's probably very low to non-existent. I'd prefer we find an option that isn't "nuke it

Re: [Chainsaw] Removal of Log4j1

if you have time Scott would be a >> manual on how to use Chainsaw and the features that it has. I >> understand it enough now, but for people first trying to use it there >> isn't really any good documentation. >> >> -Robert Middleton >> >> On Mon, Jan 17,

Re: [Chainsaw] Removal of Log4j1

Looks great! It's a lot of work for sure - lots more to do to fully remove log4j1 - custom level support (java.util.logging and Android for example), support for UI-based interactions for some receivers(activateOptions), and the loggerRepository extension pieces. I definitely want to see

Re: [Chainsaw] JSON Support

Arbitrary text formats are already supported in Chainsaw -files can be tailed locally or remotely (ssh) via a receiver that leverages Commons VFS: https://logging.apache.org/chainsaw/2.x/apidocs/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.html The receiver supports the common pattern

Re: [Chainsaw] Minor fixes

Chainsaw Mac integration leverages java9 features now (Mac prefs menu integration). I can review merge requests. On Sat, May 8, 2021, 11:19 AM Matt Sicker wrote: > It appears that Chainsaw updated its minimum Java version to 9. I'll > get that fixed in the Jenkins build. As for committing the

Chainsaw build

I've repaired the Mac UI integration and I think it's time to make a release. I'm not sure of the process, it's been forever. 'mvn clean site:site package' works fine for me on my Mac, including DMG creation. I'd like to get the DMG available to folks for download. Happy to help, Thanks,

Re: [meta] What's been going on with log4net, log4cxx, and chainsaw? Request for reports

I'll work to get that Chainsaw release out. On 2/9/21, Davyd McColl wrote: > Hi Matt > > log4net has been quite quiet over the last quarter, partly because I took a > break from all things code for a month, and partly because I'm still trying > to pick up momentum after that break! > > However,

Re: Chainsaw update

hould use an allowlist of deserializable classes. > > > That's what we did in log4j2's serialized log event receiver code a > > > few years ago, for example: > > > https://github.com/apache/logging-log4j2/commit/5dcc192 > > > (CVE-2017-5646). > > > >

Re: Chainsaw update

l) should use an allowlist of deserializable classes. > > That's what we did in log4j2's serialized log event receiver code a > > few years ago, for example: > > https://github.com/apache/logging-log4j2/commit/5dcc192 > > (CVE-2017-5646). > > > > On Sat, 7 Nov 2020

Re: Chainsaw update

I assume reverse-connect is still fine (SocketHubAppender/Receiver), as Chainsaw is being configured to reach a specific (assumed trusted) endpoint, yes? On 11/6/20, Scott Deboy wrote: > Holy cow. February? > > I have zero problem with us nuking the object serialization receiver >

Re: [CI][FAILURE] Logging/chainsaw/master#10 has potential issues

Updated to version 3 of the parent pom and clean site:site package runs fine, pushed to master. On 11/7/20, Matt Sicker wrote: > Looks like we need to either fix this pom or the parent pom. > > On Fri, Nov 6, 2020 at 21:34 Mr. Jenkins > wrote: > >> *BUILD FAILURE* >> Build URL >>

Re: Chainsaw update

wrote: > Great to hear from you again! I don’t know if you saw it but there is a > Chainsaw related email on Feb 12 of this year in the private list that you > should take a look at if you are planning on doing some work on Chainsaw. > > Ralph > > > On Nov 6, 2020, at 5:5

Chainsaw update

Hey all, Long time. I decided to work through the pom ugliness and a couple of swing degradation issues in Chainsaw. I found an ASL2 Mac dmg creation maven plugin, and it works well on my Mac, if anyone cares to try it out please do. Pushing changes to master shortly.

Re: Re-enable appbundle-maven-plugin in Chainsaw build

lugin inside a profile. Do you know how? I only discovered this issue when > writing the Jenkinsfile since I build it on macOS locally (and while > releasing). > > On 15 March 2018 at 14:58, Scott Deboy <scott.de...@gmail.com> wrote: > >> Hi Matt, >> >> Re:

Re-enable appbundle-maven-plugin in Chainsaw build

Hi Matt, Re: 1123826836323a94d73355f0f6d7fd39466ad657 - Disable macOS packaging step Looks like you disabled this to get jenkins working? Has a comment: "FIXME: make this plugin optional" Can you re-enable it? Optional is fine, I test with this all the time. Thanks, Scott

Soliciting input: ElasticSearch receiver

I'm looking at adding an ES receiver and was curious what folks would like to see when it comes to configuration options/capabilities, other than the ability to continually retrieve new events on some polling interval, which I'll make sure to add. Scott

remove Chainsaw's site code from git?

I haven't looked much at the src/site tree of Chainsaw, but it's clear that the 'real' site code in svn was seeded from Chainsaw's src/site at one point, but src/site is now stale. Can I blow that directory away and remove any site-related targets from Chainsaw's pom? Thanks, Scott

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2

Thanks Matt! Looks good! Scott On 1/25/18, Matt Sicker <boa...@gmail.com> wrote: > This vote passes with 3 +1 votes from Scott Deboy, Remko Popma, and myself. > I'll be following up with an announcement thread shortly. > > On 24 January 2018 at 18:50, Matt Sicker <bo

Re: [log4j] The shape of Log4j

+1 The added complexity of managing the various repo builds and compatibility outweighs the build-time related cost of adding this code to core, easily. Just consider the time required to RM these other repos. There is no savings here to be found. Scott On Jan 24, 2018 6:20 PM, "Remko Popma"

Re: [log4j] The shape of Log4j

My recollection is vague, tied to pom machinations supporting a similar separation for the 'log4j companions': outside of core log4j - chainsaw, component, extras, receivers and zeroconf' Some of the issues I recall having to deal with when we had the generic 'component' module: - Some classes

Re: [log4j] The shape of Log4j

Correcting my prior comment: the nightmare I was referring to was the ugliness we did and un-did related to the never-released receivers and 'component' companions. Definitely feels like deja vu. https://github.com/apache/log4j-component/blob/trunk/pom.xml apache-log4j-companions-parent etc etc

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2

+1 Pulled the git tag, built it and started Chainsaw from the standalone tarball and zips. Wandered through the website - there is cleanup to be done, but that's work that can be done post-release. Scott On 1/20/18, Matt Sicker wrote: > This is a vote to release Apache

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Sure On Jan 20, 2018 9:04 AM, "Matt Sicker" <boa...@gmail.com> wrote: > Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next > few hours. > > On 20 January 2018 at 09:47, Scott Deboy <scott.de...@gmail.com> wrote: > > > Matt, woul

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Matt, would you mind re-spinning a new build at 2.1.0-rc1? On 1/19/18, Scott Deboy <scott.de...@gmail.com> wrote: > I finally looked at this. I pushed a change to app assembler config > to make the bin directory executable, and updated HOWTOBUILD to > mention you need to run mvn

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

oads page needs to be updated to > link to the (future) dist URLs instead of ones in the site's directory (no > proper mirroring in the old links). > > On 12 November 2017 at 19:25, Scott Deboy <scott.de...@gmail.com> wrote: > >> I don't recall why - it was a while back :

Re: Log4JNA

+1 On Nov 23, 2017 10:20 AM, "Ralph Goers" wrote: > Or ask the author if he would like it to become part of Logging Services. > > Ralph > > > On Nov 23, 2017, at 7:51 AM, Gary Gregory > wrote: > > > > On Thu, Nov 23, 2017 at 4:10 AM, Remko

Re: [Chainsaw] Next step: Log4j 2

Awesome! Re: appenders: We went through a couple of code re-orgs back in 2011 and 2013, some stuff was moved out of Chainsaw to apache-log4j-extras. Looks like some was left behind. You can define Chainsaw as an appender yourself - so the UI starts if it's in the log4j xml config file.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I don't recall why - it was a while back :) Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory issue. On 11/12/17, Matt Sicker <boa...@gmail.com> wrote: > On 12 November 2017 at 13:53, Scott Deboy <scott.de...@gmail.com> wrote: > >> That's right

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

That's right -forgot we rev'd to 2.1 internally (info.plist, release notes, couple other places). Would it be easiest to release the new version as 2.1.0.0 instead of 2.0.0-rc1? Otherwise I could downgrade 2.1 refs, we never had an official release with that rev. Scott On 11/12/17, Mikael

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I think we can either fix or remove that menu item from the menu after the release - I don't know how useful it is. Scott On 11/12/17, Mikael Ståldal wrote: > When starting Chainsaw, I see this warning: > > Could not find any local JavaDocs, you might want to consider running

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Fixed. On 11/12/17, Mikael Ståldal wrote: > In the About text, it says: > > Please send questions, bug reports and/or feature requests to > log4j-...@logging.apache.org > > which is obsolete. > > > On 2017-11-10 20:00, Matt Sicker wrote: >> This is a vote to release Apache

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

That's right - we don't bundle in a JMS jar, although users can add one to the classpath to use the JMSReceiver. On 11/12/17, Mikael Ståldal wrote: > When running Chainsaw, I see this error message: > > Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks >

Re: Planning out what we can do to get Chainsaw back in the game

definitely get Chainsaw back in the game. I think you would have an >>>> easy >>>> time attracting a talent pool for something like that. For example >>>> http://akveo.github.io/blur-admin/ is currently available on Github and >>>> has 8000 st

Re: Planning out what we can do to get Chainsaw back in the game

I think you would have an easy > time attracting a talent pool for something like that. For example > http://akveo.github.io/blur-admin/ is currently available on Github and > has 8000 stars. Could be the starting point for the next generation > logging UI. > > Cheers, > >

Re: Planning out what we can do to get Chainsaw back in the game

I'd love to hear what folks think of the user experience with the 'latest Chainsaw' and its feature set. There are a ton of features. It will be interesting to get a sense of how many of those features we get 'for free' in any of these other UI toolkits. It was a lot of heavy lifting to get

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I had ran mvn clean site:site install and it worked. On 11/11/17, Mikael Ståldal wrote: > On 2017-11-10 20:00, Matt Sicker wrote: >> Artifacts: >> https://dist.apache.org/repos/dist/dev/logging/chainsaw/ >> svn revision 23048 > > When I look at that URL, it says: Revision

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Here's my +1. Site looks good, and it builds and runs. Thanks Matt On 11/10/17, Scott Deboy <scott.de...@gmail.com> wrote: > Updated screenshot. > > On 11/10/17, Scott Deboy <scott.de...@gmail.com> wrote: >> Awesome..I'll commit a new screenshot then. >> >

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Updated screenshot. On 11/10/17, Scott Deboy <scott.de...@gmail.com> wrote: > Awesome..I'll commit a new screenshot then. > > On 11/10/17, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> The web site doesn’t have to be locked into the release. An image can be &

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Would it be possible for me to push an updated screenshot and re-spin? On 11/10/17, Scott Deboy <scott.de...@gmail.com> wrote: > Wow that screen shot looks ancient and ugly. I should pull up > something on the Mac with updated default colors - it looks much > better. > >

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Wow that screen shot looks ancient and ugly. I should pull up something on the Mac with updated default colors - it looks much better. Scott On 11/10/17, Matt Sicker wrote: > Oh, and in case it isn't obvious how to test this, you can extract from > either the zip or tar.gz

Re: Planning out what we can do to get Chainsaw back in the game

FYI, I think most folks just use pattern layout, which probably makes VFSLogFilePatternReceiver the most commonly used receiver. Since it's VFS, anything accessible over SSH is retrievable and can be live-tailed. Also, Chainsaw V2 can pull in logs generated by Log4j2 if you configure an

Re: Planning out what we can do to get Chainsaw back in the game

present at all in log4j2, are found throughout the code. A json receiver would be great! Me, I've been working on a private cloud IaaS implementation for a few years now - almost no Java there. Scott On 10/14/17, Matt Sicker <boa...@gmail.com> wrote: > On 14 October 2017 at 13:28, Sc

Re: Planning out what we can do to get Chainsaw back in the game

Try out Chainsaw - it's super useful once you get the model. Under help, there's info on the expression syntax, and the chainsaw-log tab (where chainsaw log messages route by default) can be a playground for working with the colorization/filtering/expressions. Here's my general flow: 1. Filter

Re: Attempting to change consumers of Log4j 2 SerializedLayout

Chainsaw supports log4j1's xml format over UDP and TCP, as well as any regular text format via (VFS)LogFilePatternReceiver. It also supports log4j1's serialized loggingevent format. Chainsaw integration with Logj42 is via VFSLogFilePatternReceiver - you have to specify the pattern and an

Re: Chainsaw in git

t; > > > (Shameless plug) Every java main() method deserves http://picocli.info > > > >> On May 31, 2017, at 8:54, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> > >> At the request of Scott Deboy I have migrated chainsaw to git. You ca

Re: Status of Chainsaw

I continue to tweak it occasionally, not much lately. Not updating release because I never got around to branding. The dmg is for x86 but I've been updating snapshots on people. It has a lot of good features now but has warts (timestamp parsing slowness mostly). I will continue to tweak it but

Re: [VOTE] EOL for Log4j 1.x

+1 On Jul 11, 2015 8:29 AM, Ralph Goers ralph.go...@dslextreme.com wrote: +1 Ralph On Jul 11, 2015, at 7:15 AM, Christian Grobmeier grobme...@apache.org wrote: Hello all, as previously discussed, this is a vote to label Log4j 1.x as EOL. This means: 1. label Log4j 1.x as

Re: [chainsaw] Code Signing Services

Yes - infra finally finished this! I've already filed a jira. https://issues.apache.org/jira/browse/INFRA-8439 Maybe we will finally get this out the door. Scott Scott On Oct 16, 2014 5:11 AM, Christian Grobmeier grobme...@gmail.com wrote: Hi all, specifically this is a question to Scott:

Requesting Chainsaw code signing cert

FYI, I filed https://issues.apache.org/jira/browse/INFRA-8439 - Logging Services Chainsaw code signing support Scott - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail:

Re: [5/7] git commit: Note correct signing key for distribution.

Chainsaw is actually the immediate need for the code signing cert. Scott On Aug 29, 2014 9:19 PM, Ralph Goers ralph.go...@dslextreme.com wrote: Why can’t it be used to sign release artifacts? Ralph On Aug 29, 2014, at 7:55 PM, Matt Sicker boa...@gmail.com wrote: Oh that's definitely a

Re: [VOTE] Switch Log4j2 to Git

+1 On Aug 5, 2014 7:18 AM, Matt Sicker boa...@gmail.com wrote: This topic was brought up elsewhere, so I'd like to propose a vote on switching to Git. +1 for me -- Matt Sicker boa...@gmail.com

Re: Finding free ports

+1 On 6/26/14, Gary Gregory garydgreg...@gmail.com wrote: Or you could not run tests in parallel and keep it simple. This is not a problem that needs solving and make the code harder to understand and maintain. Gary On Thu, Jun 26, 2014 at 4:50 PM, Matt Sicker boa...@gmail.com wrote: A

Re: debug output

+1 On Jun 15, 2014 4:05 PM, Ralph Goers ralph.go...@dslextreme.com wrote: Do we need the builders? As I said, I prefer only one way for creating plugins. Ralph On Jun 15, 2014, at 2:49 PM, Remko Popma remko.po...@gmail.com wrote: I see. I agree that the original format is much nicer.

Re: [jira] [Commented] (LOG4J2-665) Unable to connect from log4j2 Client GUI to my application

I'd suggest trying the latest developer snapshot of Chainsaw, available at http://people.apache.org/~sdeboy Scott On Jun 11, 2014 8:56 AM, Arthur Hsieh (JIRA) j...@apache.org wrote: [

[jira] [Commented] (LOG4J2-665) Unable to connect from log4j2 Client GUI to my application

[ https://issues.apache.org/jira/browse/LOG4J2-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028637#comment-14028637 ] Scott Deboy commented on LOG4J2-665: I'd suggest trying the latest developer snapshot

Re: Working on support for the properties file format.

We shouldn't close feature requests as won't fix. Someone may come along later and decide to implement it. It's ok to say no one is planning on working on the feature, and remind the submitter that patches are welcome. Scott Scott On Jun 9, 2014 6:46 AM, Paul Benedict pbened...@apache.org

Re: [VOTE Results] Log4j 2 logo

+1 On Jun 6, 2014 10:07 PM, Matt Sicker boa...@gmail.com wrote: I like both logos, so I'm good with however you guys would like to go. Vote or not. On 6 June 2014 20:57, Remko Popma remko.po...@gmail.com wrote: Scott, Matt, what do you think? On Sat, Jun 7, 2014 at 10:48 AM, Ralph Goers

Re: [VOTE] Log4j 2 logo

And mine: DBAHCIEFG On 6/3/14, Ralph Goers ralph.go...@dslextreme.com wrote: In case it is not clear, the names (Aragorn, etc) below are for some other fictional vote to illustrate how to vote Here is my vote: DABIEFHGC Ralph On Jun 3, 2014, at 1:08 PM, Ralph Goers

Re: Can any PMCs or chairs take a look at this?

Nope, it just shows my personal repositories, even though I am part of the 'Apache' organization in GitHub. On 4/14/14, Matt Sicker boa...@gmail.com wrote: https://travis-ci.org/apache/logging-log4j2 If you log in with your GitHub account, does it give you any administrative options?

Re: org.apache.log4j.net.XMLSocketReceiver from v1

We need to add receivers to log4j2 :) Dcott On Mar 25, 2014 5:19 AM, Gary Gregory garydgreg...@gmail.com wrote: Hi All: Our server uses v1's org.apache.log4j.net.XMLSocketReceiver. I do not see a v2 equivalent. Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org

Re: Are there any plans to add more log4languages?

Many of those already exist outside of Apache. Scott On Mar 14, 2014 2:29 PM, Matt Sicker boa...@gmail.com wrote: I see we have log4j, log4net, log4php, and log4cxx. How about Python, Ruby, Perl, etc.? Anything incubating? Anyone interested in working on one? -- Matt Sicker boa...@gmail.com

Re: Health

Hi Ralph, Glad to hear you're getting better! Scott On 2/21/14, Gary Gregory garydgreg...@gmail.com wrote: Ralph, It is great to hear that you are out of the hospital! Please do take care of yourself and don't overdo it ;) Log4J can wait... :) Gary On Fri, Feb 21, 2014 at 12:19 AM,

Re: [VOTE] Log4j 2.0-rc1 RC2

: TimeBasedTriggeringPolicy should use event time millis. Thanks to Robin Zhang Tao. o LOG4J2-472: BaseConfiguration class does not properly implement Configuration interface. Thanks to Tal Liron. o LOG4J2-447: XMLLayout does not include marker name. Thanks to Jeff Hudren, Mark Paluch, Scott Deboy

Re: [VOTE] Log4j 2.0-rc1 RC2

I'll check it out..apologies! On 2/11/14, Remko Popma remko.po...@gmail.com wrote: Gentle reminder: we need one more PMC vote to be able to release. On Tuesday, February 11, 2014, Christian Grobmeier grobme...@gmail.com wrote: I think Rat is wrong on the jquery license. They have included

Re: [VOTE] Log4j 2.0-rc1 RC2

+1 (site looks good, tag built fine with mvn install, artifacts look good) Scott On 2/11/14, Scott Deboy scott.de...@gmail.com wrote: I'll check it out..apologies! On 2/11/14, Remko Popma remko.po...@gmail.com wrote: Gentle reminder: we need one more PMC vote to be able to release

Re: CouchDb vs CouchDB

couchbase it I won't veto it. Be sure to change the test package name, too. Nick On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote: +1 to couchbase On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com wrote: On 7 Feb 2014, at 16:19, Nick Williams wrote: It doesn't so much matter

Re: CouchDb vs CouchDB

veto with technical justification. Since I can't come up with a technical justification for renaming it to couchbase, I won't veto it. :-) N On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote: I do want to remind everyone that vetoes are only valid if they are backed by a technical justification

Re: CouchDb vs CouchDB

+1 to couchbase On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com wrote: On 7 Feb 2014, at 16:19, Nick Williams wrote: It doesn't so much matter because the XML element names are case insensitive, but if we change the plugin name for CouchDB we should probably also change it

Re: Logger setLevel?

Add setlevel. I also think appender belongs in Api. Yes? On Jan 31, 2014 10:01 AM, Gary Gregory garydgreg...@gmail.com wrote: Porting from v1... We do not have Logger setLevel(Level) because it is not in the LCD API (Slf4j no, Logback yes, JUL yes). This sure makes it a pain to port from

Re: Logger setLevel?

Re: appenders, I was thinking about Remko's response here: http://stackoverflow.com/questions/21303746/migrating-from-log4j-1-2-to-log4j-2-how-to-get-list-of-all-appenders-and-rolli On 1/31/14, Gary Gregory garydgreg...@gmail.com wrote: On Fri, Jan 31, 2014 at 1:05 PM, Scott Deboy scott.de

Re: Enums and Custom Levels - completed.

So I assume we could build on this by adding the ability to generate these custom levels from the config, with no user provided class required? On Jan 26, 2014 12:58 AM, Ralph Goers ralph.go...@dslextreme.com wrote: I have completed the work on custom levels. It uses a variation of Nick’s

Re: Enums and Custom Levels - completed.

, 2014 7:28 AM, Scott Deboy scott.de...@gmail.com wrote: So I assume we could build on this by adding the ability to generate these custom levels from the config, with no user provided class required? On Jan 26, 2014 12:58 AM, Ralph Goers ralph.go...@dslextreme.com wrote: I have completed

Re: Enums and Custom Levels - completed.

to directly do that. However, custom levels need to be mapped to the standard levels in several places. It would be simple to add support for that wherever you want it. Level.StdLevel.getStdLevel() is the method used to do that. Ralph On Jan 26, 2014, at 7:45 AM, Scott Deboy scott.de...@gmail.com

Re: Enums and Custom Levels - completed.

entail adding a new Levels element, with sub-elements like Level name=DETAIL intLevel=450 /... Is that what you are thinking of? I would be fine with that too, but would like to first focus on generating the extended Logger interface. On Mon, Jan 27, 2014 at 5:29 AM, Scott Deboy scott.de

Re: Enums and Custom Levels - completed.

that implementation so that it doesn't have to be implemented again, and then instantiate/cache the logger instance like normal. Make sense? N On Jan 26, 2014, at 5:32 PM, Scott Deboy wrote: Yes that's what I was thinking. Scott On Jan 26, 2014 3:18 PM, Remko Popma remko.po...@gmail.com wrote

  1   2   3   4   5   6   >