+1 to what Ralph said
On Sat, Sep 30, 2023 at 0:56 Scott Deboy wrote:
> +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
Yes, it was mostly to get rid of the log4j1 dependency and to get rid
of/update other dependencies. There are a number of parts of chainsaw that
depend on log4j1 features which may or may not be relevant.
Most of the UI functionality should still exist, as far as I am aware. I
think some of the
> On Sep 29, 2023, at 6:10 AM, Christian Grobmeier wrote:
>
>
> On Fri, Sep 22, 2023, at 12:51, Christian Grobmeier wrote:
>> On Thu, Sep 21, 2023, at 19:38, Ralph Goers wrote:
>>> At this point in time I will abstain from voting. As far as I am
>>> concerned only 1 vote counts - Scott’s.
+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.
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. Almost 100% of
the stuff Matt has done would never have happened.
It is a fact that
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'
Hi,
Looking through the code base, I saw lots of code that is commented. Some
classes (maybe because of this) are not even used anymore. I only saw one class
(ChainsawViewer), which might make sense to keep.
Is it OK to remove this all? Or is there a specific reason for this?
Some methods are
+1
On Fri, Sep 29, 2023, at 13:13, Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Tools 0.5.0.
>
> Source repository: https://github.com/apache/logging-log4j-tools
> Commit: 861b03c70a76ca19408ffc8c4a77bc0c4e5e4570
> Distribution:
Oh wow I was sure this is log4j1 great, I even found some docs.
https://logging.apache.org/log4j/2.x/manual/configuration.html#chainsaw-can-automatically-process-your-log-files-advertising-ap
Thanks!
On Fri, Sep 29, 2023, at 21:40, Scott Deboy wrote:
> This is a log4j2 feature.
>
> Scott
>
>
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?
>
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?
I think Jira is good enough for that, since there is transition from state
to state that can be used to shepherd issues through. RFC, JEP, all way too
heavy handed for us IMO.
Gary
On Fri, Sep 29, 2023, 2:05 PM Matt Sicker wrote:
> I think it could be valuable for us to establish some form of
I think it could be valuable for us to establish some form of an RFC process
for proposing and developing major new features. I also want to avoid being too
process-heavy here as that would also disincentivize contributions. I agree
that we should try to be more data-driven to determine what
+1
> On Sep 29, 2023, at 6:13 AM, Volkan Yazıcı wrote:
>
> This is a vote to release the Apache Log4j Tools 0.5.0.
>
> Source repository: https://github.com/apache/logging-log4j-tools
> Commit: 861b03c70a76ca19408ffc8c4a77bc0c4e5e4570
> Distribution:
On Fri, Sep 29, 2023, at 18:51, Scott Deboy wrote:
> There should be a default config. Do you have anything in the .chainsaw
> directory? If so, delete it.
Yes figured it right when I received your message.
The application created this directory. Looking into it, there were files as
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"));
>
OK, got it running, after commenting those lines:
//statusBar.setSelected(config.getBoolean("statusBar"));
statusBar.setSelected(false);
//receivers.setSelected(config.getBoolean("showReceivers"));
receivers.setSelected(false);
//toolBar.setSelected(config.getBoolean("toolbar"));
I have installed Netbeans and tried it with that.
I also tried Corretta 11, Zulu 11, Zulu 11 with FX. OpenJDK 11 is no longer
available for me (on Mac) it seems.
Still no success. The splash opens, but no further movement.
I have two errors earlier, but I don't think they break anything:
No. If the build would have failed, I couldn't cut the release, since it is
the CI uploading artifacts + distribution to both Nexus and SVN. Probably
an issue with the badge or sth else on `main`.
On Fri, 29 Sep 2023, 16:24 Gary Gregory wrote:
> https://github.com/apache/logging-log4j-kotlin
It starts up for me with Netbeans and OpenJDK 11. I would expect an
exception/stack trace to be printed to stderr if an exception was thrown
that caused it to fail to load.
-Robert Middleton
On Fri, Sep 29, 2023 at 9:17 AM Christian Grobmeier
wrote:
> Hi,
>
> I have found out Chainsaw
https://github.com/apache/logging-log4j-kotlin shows the "build failing"
badge, does that matter?
Gary
On Thu, Sep 28, 2023, 9:25 AM Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Kotlin API 1.3.0.
>
> Source repository: https://github.com/apache/logging-log4j-kotlin
>
Hi,
I have found out Chainsaw requires Java 11. I used this from IntelliJ and run
LogUI.
However, even when there is no error message, the Splash Screen never
disappears.
Is there any specific verion of Java I need?
These are he last lines i see:
15:15:29.580 [AWT-EventQueue-0] DEBUG
On Fri, Sep 22, 2023, at 12:51, Christian Grobmeier wrote:
> On Thu, Sep 21, 2023, at 19:38, Ralph Goers wrote:
>> At this point in time I will abstain from voting. As far as I am
>> concerned only 1 vote counts - Scott’s. He has steadfastly asked that
>> the project not be retired and until
I see your point and agree with many things. I suggest we are not (only) making
"data-driven" decisions. Most of us do this for fun, not for money. It is
perfectly OK to decide just because we like it and enjoy ourselves.
You are raising an excellent point: maintenance.
We have a lot of stuff
+1
--
The Apache Software Foundation
V.P., Data Privacy
On Thu, Sep 28, 2023, at 15:26, Volkan Yazıcı wrote:
> This is a vote to release the Apache Log4j Kotlin API 1.3.0.
>
> Source repository: https://github.com/apache/logging-log4j-kotlin
> Commit: b273cfb450898f079d2fd10b575330bfb900101b
>
This is a vote to release the Apache Log4j Tools 0.5.0.
Source repository: https://github.com/apache/logging-log4j-tools
Commit: 861b03c70a76ca19408ffc8c4a77bc0c4e5e4570
Distribution: https://dist.apache.org/repos/dist/dev/logging/log4j-tools
Nexus:
I want to challenge the current way of PMC determining the product feature
set and work towards a more sustainable alternative.
Logging Services team...
- delivers mission-critical products that are deployed at the core of
the world-wide infrastructure (actually, in Mars too)
- is short
27 matches
Mail list logo
