[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205050#comment-16205050
]
ASF subversion and git services commented on LOG4J2-2056:
-
Commit
[
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 aut
I have committed the code for LOG4J2-2056. Log4j-api is a “real” module and has
a module-info.java while all the rest that can be modularized are automatic
modules. Please review and test.
In order to create the module-info.java I had to do a few strange things:
Module-info.java is in the log4j
[
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
modul
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 pr
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204848#comment-16204848
]
Ralph Goers edited comment on LOG4J2-2056 at 10/14/17 11:09 PM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204848#comment-16204848
]
Ralph Goers commented on LOG4J2-2056:
-
Another thought. Log4j allows the log4j api an
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 a
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 the
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 this: <
http://www.scalafx.o
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 2017 at 21:57, kenne
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 five parts:
>
> - Recei
Awesome! Happy to help here where I can, although I haven't worked in
Java in forever.
Chainsaw is really five parts:
- Receivers which grab the data from whatever source
- The 'route events to tabs' mechanism
- Table/event rendering, including search/filter/colorization and
time deltas betwe
+1
Small increments seem prudent until there is some understanding of where we
want to go.
Ralph
> On Oct 14, 2017, at 11:10 AM, Gary Gregory wrote:
>
> Hi Matt,
>
> It seems to me that to get out of the mess we are currently in, we need to
> publish something official ASAP, even it is just
I’ve worked with JavaFX. It is pretty easy. I have zero interest in working
with Swing.
I’d prefer to get away from WebStart. I think that may have been what hung up
Scott in the first place as he needed a cert. Some of the other technologies
for binary deployment make sense to me.
To be hones
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 appears we may
> already
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 13
I would really stay away from Java 9 at this point. There is too much
incompatible tooling out there at this point. I can't even run most apps
out of the box I have laying around on Java 9 without breakage.
Gary
On Sat, Oct 14, 2017 at 12:09 PM, Matt Sicker wrote:
> I forgot to mention my curre
Hi Matt,
It seems to me that to get out of the mess we are currently in, we need to
publish something official ASAP, even it is just an alpha or beta.
Toward this goal, we should make the least amount of changes as possible.
Changing the source to 1.6 seems like a requirement to use modern toolin
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 13:01,
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 2017 at 21:57, kenneth mcfarland
wrote:
> My bad, here is a link sir.
>
> http://code.revelc.net/impsort-maven-plugin/
>
> On Fri, Oct 13, 2017 at 7:35 PM, Matt Si
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 Sicker wrote:
> >
> > I almost
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 po
[
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204740#comment-16204740
]
ASF subversion and git services commented on LOG4J2-1431:
-
Commit
[
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 propert
[
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 envi
[
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204743#comment-16204743
]
ASF subversion and git services commented on LOG4J2-1431:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204742#comment-16204742
]
ASF subversion and git services commented on LOG4J2-1809:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204741#comment-16204741
]
ASF subversion and git services commented on LOG4J2-1431:
-
Commit
29 matches
Mail list logo
