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

On 14 October 2017 at 13:22, Ralph Goers wrote: > I’ve worked with JavaFX. It is pretty easy. I have zero interest in > working with Swing. > Good to know! For Kotlin support, this project looks handy: < https://github.com/edvin/tornadofx>. For Scala support, there's

[jira] [Comment Edited] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204848#comment-16204848 ] Ralph Goers edited comment on LOG4J2-2056 at 10/14/17 11:09 PM: Another

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

I also opened a ticket about the bugzilla to jira part: https://issues.apache.org/jira/browse/INFRA-15282 On 14 October 2017 at 13:15, Matt Sicker wrote: > I'm looking at the infra stuff right now. Found this: < > https://issues.apache.org/jira/browse/INFRA-8439>. So it

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

I'm looking at the infra stuff right now. Found this: < https://issues.apache.org/jira/browse/INFRA-8439>. So it appears we may already have the webstart code signing thing handled. More info here: < https://blogs.apache.org/infra/entry/code_signing_service_now_available>. On 14 October 2017 at

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204740#comment-16204740 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204741#comment-16204741 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

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

First off, for some reason, there are two repositories: https://github.com/apache/chainsaw https://github.com/apache/logging-chainsaw The second one appears to be up to date. Not sure what to do about the first one as it seems to be a relic of when Chainsaw was in SVN. Next, bug tracking. The

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

I forgot to mention my current difficulty in the release process are broken tests. I just noticed that my default Java version on this computer is actually 9, not 8, so that could be related. Any guidance from anyone who's successfully built this before would be great. On 14 October 2017 at

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

Greetings, I have been trying to find someone who can do the Apache mentor program with me (link provided). The mentor only does roughly 1/4 the time of the mentee, the mentee comes prepared to dedicate the time and put the work in and provide progress reports etc.. GSoC is over obviously, but

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: Import Ordering - ImpSort

Thank you Matt, I will try provide a patch by the end of the weekend. Cheers, Kenneth On Oct 14, 2017 11:02 AM, "Matt Sicker" wrote: > That looks like it could be useful for sure. It could help avoid merge > conflicts. I say go for it and provide a patch! > > On 13 October

[jira] [Resolved] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1431. - Resolution: Fixed Fix Version/s: 2.10.0 Merged to master. > Simplify log4j system

[jira] [Resolved] (LOG4J2-1809) Add global configuration environment SPI

[ https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker resolved LOG4J2-1809. - Resolution: Fixed Fix Version/s: 2.10.0 Merged to master. > Add global configuration

[jira] [Commented] (LOG4J2-1431) Simplify log4j system property naming scheme

[ https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204743#comment-16204743 ] ASF subversion and git services commented on LOG4J2-1431: - Commit

Re: [Log4j] Next release?

I merged my properties branch. Started a new thread about Chainsaw. On 12 October 2017 at 16:03, Ralph Goers wrote: > Please do work on Chainsaw. Of course, that isn’t related to a Log4j > release (or vice versa). > > Ralph > > > On Oct 12, 2017, at 1:53 PM, Matt

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

On 14 October 2017 at 13:28, Scott Deboy wrote: > Awesome! Happy to help here where I can, although I haven't worked in > Java in forever. > Are you using any other JVM languages regularly? Or have you gone down the native code route or something? > Chainsaw is really

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

Parsing time strings to their numeric values using SimpleDateFormat is painfully slow - I don't even use it any longer when I'm looking at 1M+ rows in Chainsaw. Implementation wise I wrote this in the heyday of Logrj1, so LoggingEvent and a few other features of Log4j1, a number of which aren't

[jira] [Updated] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2056: Description: To fully support Java 9 all Log4j jars must (at least) be packaged as automatic

[jira] [Resolved] (LOG4J2-2056) Modularize Log4j as automatic modules

[ https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2056. - Resolution: Fixed Fix Version/s: 2.10.0 Fix has been committed. > Modularize Log4j as