t; I do have a task to upgrade Flume as well as add a fix for a problem that was
> reported. As you know we use Flume at my work and it needs to be upgraded. So
> I will be jumping back on this in the next couple of months.
>
> I don’t work on Chainsaw and never have. I don’t know
nged for the other log4j projects.
>
> I do have a task to upgrade Flume as well as add a fix for a problem that was
> reported. As you know we use Flume at my work and it needs to be upgraded. So
> I will be jumping back on this in the next couple of months.
>
> I don’t work on
on Chainsaw and never have. I don’t know of anyone who plans to do
any work on it so I do not object to archiving chainsaw.
I do have to apologize. While I try to follow the dev l& pmc lists I have had a
terrible time following the email generated by GitHub. I currently have almost
10
t; -1 on Flume
>
> Despite you not seeing visible evidence I am still working on these. I am
> actually fairly confident I will need to create releases of Flume in the
> next 6 months.
>
> Ralph
>
> > On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı wrote:
> >
> >
-1 on Flume
Despite you not seeing visible evidence I am still working on these. I am
actually fairly confident I will need to create releases of Flume in the next 6
months.
Ralph
> On Jan 15, 2025, at 2:05 AM, Volkan Yazıcı wrote:
>
> Chainsaw and Flume projects have been moved t
Hi Volkan,
On 15.01.2025 10:03, Volkan Yazıcı wrote:
*I suggest archiving¹ `logging-chainsaw` and `logging-flume*` GitHub
repositories. Objections?*
+1
Could you also archive/remove the `2.3.x` and `2.12.x` web pages. As
recent questions show, these are still used.
Piotr
Chainsaw and Flume projects have been moved to dormant state with PMC
consensus. Yet their GitHub repositories (i.e., `logging-chainsaw` and
`logging-flume*`) don't reflect this and they weekly get flagged by GitHub
due to vulnerable dependencies. This is also confusing for users, since the
I have moved Chainsaw to the dormant section on the main website:
https://logging.apache.org/
There is a label missing on the CS website itself, but I will have similar work
in future, so I am going to do it together with that
On Fri, Feb 16, 2024, at 09:56, Christian Grobmeier wrote:
>
Chainsaw to dormant
Date: Monday, February 12, 2024 22:31
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 better to move Chains
+1
Thanks!
-ck
On Mon, Feb 12, 2024, at 16:31, Christian Grobmeier wrote:
> 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
On Tue, Feb 13, 2024, at 05:09, Tim Perry wrote:
> Do dormant projects clearly indicate they can be re-animated by a
> sufficient number of active committers?
In the case of Chainsaw and Log4php, I don't see any issues with it, and if
people are willing to maintain it (not only short
+1
On Mon, Feb 12, 2024 at 10:32 PM 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
Do dormant projects clearly indicate they can be re-animated by a sufficient
number of active committers?
Thanks,
Tim
+1
Gary
On Mon, Feb 12, 2024 at 4:32 PM 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
+1
Piotr
On Mon, 12 Feb 2024 at 22:32, 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
+1
Ralph
> On Feb 12, 2024, at 2:31 PM, 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
+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 sit
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 better to move Chainsaw to
the dormant section and communicate it as
gt;>
>>
>> On Wed, Feb 7, 2024 at 5:19 AM Scott Deboy wrote:
>>
>>> 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
ne.html>
> to achieve that.
>
>
> On Wed, Feb 7, 2024 at 5:19 AM Scott Deboy wrote:
>
> > Thank you for spending time working on it Christian.
> >
> > I started contributing to Chainsaw in 2003. I agree. It's time.
> >
> > The primary benefit
ide/en/logstash/current/advanced-pipeline.html>
to achieve that.
On Wed, Feb 7, 2024 at 5:19 AM Scott Deboy wrote:
> 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 Chainsa
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
Hello
we have had Chainsaw for a long time in our product list, and I can totally see
that some - myself included - are emotionally attached to it. However, due to
my work on it, I have given it some additional thought.
After working with the Chainsaw code base for a while, I saw that many
sion
event routing mechanism and the ability to hide and show columns.
Scott
On 12/2/23, Christian Grobmeier wrote:
> Hi,
>
> I re-added the load/write feature in ChainsawTabbedPane using JSON and
> Genson:
> https://github.com/apache/logging-chainsaw/blob/master/src/main/java/
Hi,
I re-added the load/write feature in ChainsawTabbedPane using JSON and Genson:
https://github.com/apache/logging-chainsaw/blob/master/src/main/java/org/apache/log4j/chainsaw/components/tabbedpane/ChainsawTabbedPane.java#L126-L191
If it works, I will refactor it further so we can reuse the
Thank you Scott,
It is very encouraging you are joining this effort! Now I feel more confident
we can make a new release!
I am doing my best to learn more about Chainsaw and contribute further!
On Wed, Nov 29, 2023, at 20:13, Scott Deboy wrote:
> I'll go through the UI and re-add small
drag), and I've added VFSLogFilePatternReceiver support and it works
> fine.
>
> To test VFSLogFilePatternReceiver:
> * Start Chainsaw
> * View, Show Receivers menu
> * Hit the 'create' icon in the receivers pane
> * Select 'New VFSLogFilePatternReceiver'
&g
I've fixed the logger tree split pane UI (left artifacts when you
drag), and I've added VFSLogFilePatternReceiver support and it works
fine.
To test VFSLogFilePatternReceiver:
* Start Chainsaw
* View, Show Receivers menu
* Hit the 'create' icon in the receiver
Hi Scott,
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
On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote:
>
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
not ready to release a new version, nor do we know what is necessary to
release one.
We have lots of dead code in Chainsaw, and it is tough to understand "what
should it do?"
I move around many Swing components to understand better, because the code is
complex. However, I didn
ten these days
> I'm not sure exactly what it does/how it does it, but it's going to
> effectively do something like "SELECT * FROM Logs" and then pass those
> log messages up to other parts of chainsaw.
I see. So the job would be to check how log4j2 appenders works, and
On Tue, Oct 24, 2023, at 22:19, Matt Sicker wrote:
> If you use Log4j in Chainsaw, you could set up a JDBC appender or
> similar to forward things along. The Flume appender could be useful
> there, too, but that sort of moves the database configuration into your
> Flume config.
quot; and then pass those
log messages up to other parts of chainsaw.
-Robert Middleton
On Tue, Oct 24, 2023 at 4:20 PM Matt Sicker wrote:
>
> If you use Log4j in Chainsaw, you could set up a JDBC appender or similar to
> forward things along. The Flume appender could be useful there,
If you use Log4j in Chainsaw, you could set up a JDBC appender or similar to
forward things along. The Flume appender could be useful there, too, but that
sort of moves the database configuration into your Flume config.
> On Oct 24, 2023, at 3:14 PM, Christian Grobmeier wrote:
>
> Hi
Hi,
in this package:
org.apache.log4j.db
all classes are commented. I am tempted to just remove it in full, but I am not
sure what i was supposed to do.
Docs read:
"Provides means to append logging events into various databases."
Does that mean, Chainsaw would collect logs and th
gt; Note, you can also define 'expression views', like DB views, where an
> event matching the expression is added to the expression view tab, but
> that's on top of the default routing.
>
> On 10/13/23, Robert Middleton wrote:
>> For those of you who didn't see
outed.
Note, you can also define 'expression views', like DB views, where an
event matching the expression is added to the expression view tab, but
that's on top of the default routing.
On 10/13/23, Robert Middleton wrote:
> For those of you who didn't see on slack: I did update
For those of you who didn't see on slack: I did update Chainsaw last
night so you can load/save receivers. That brings Chainsaw back into
a usable state(in my mind at least). I need to check to ensure that
everything gets saved properly, but that shouldn't be too hard.
Scott, woul
; >>> >> serialized
>> >>> >> map. Removing the java serialization is important.
>> >>> >
>> >>> > OK. Do you think something based on Jackson would be good? It's JSON
>> >>> > though.
>> >>> >
g the java serialization is important.
> >>> >
> >>> > OK. Do you think something based on Jackson would be good? It's JSON
> >>> > though.
> >>> >
> >>> > From an example:
> >>> >
> >>> >
>>> > From an example:
>>> >
>>> > ObjectMapper objectMapper = new ObjectMapper();
>>> > Car car = new Car("yellow", "renault");
>>> > objectMapper.writeValue(new File("target/car.json"), car);
>>> >
&
quot;target/car.json"), car);
>> >
>> > We could wrap this in some kind of class and make it accessible per
>> > "tab" (or whatever).
>> >
>> >
>> >>
>> >> -Robert Middleton
>> >>
>> >>
rap this in some kind of class and make it accessible per "tab"
> > (or whatever).
> >
> >
> >>
> >> -Robert Middleton
> >>
> >> On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier
> >> wrote:
> >>
> >>>
>
n
>>
>> On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier
>> wrote:
>>
>>>
>>> On Mon, Oct 2, 2023, at 02:55, Robert Middleton wrote:
>>>> Some(most?) of the settings should be saved:
>>>>
>>> https://github.com/apache
Mapper.writeValue(new File("target/car.json"), car);
>>
>> We could wrap this in some kind of class and make it accessible per "tab"
>> (or whatever).
>>
>>
>>>
>>> -Robert Middleton
>>>
>>> On Mon, Oct 2, 2023 at
w File("target/car.json"), car);
>
> We could wrap this in some kind of class and make it accessible per "tab"
> (or whatever).
>
>
>>
>> -Robert Middleton
>>
>> On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier
r
whatever).
>
> -Robert Middleton
>
> On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier
> wrote:
>
>>
>> On Mon, Oct 2, 2023, at 02:55, Robert Middleton wrote:
>> > Some(most?) of the settings should be saved:
>> >
>> https://
ost?) of the settings should be saved:
> >
> https://github.com/apache/logging-chainsaw/blob/5ccb3c8e55dffd4361c549c3bcdac3f3675f79e5/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java#L191
> >
> > The stuff that is commented out should just be the old saving code
On Mon, Oct 2, 2023, at 02:55, Robert Middleton wrote:
> Some(most?) of the settings should be saved:
> https://github.com/apache/logging-chainsaw/blob/5ccb3c8e55dffd4361c549c3bcdac3f3675f79e5/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java#L191
>
> The stuff that
Some(most?) of the settings should be saved:
https://github.com/apache/logging-chainsaw/blob/5ccb3c8e55dffd4361c549c3bcdac3f3675f79e5/src/main/java/org/apache/log4j/chainsaw/prefs/SettingsManager.java#L191
The stuff that is commented out should just be the old saving code that
used XStream to
On Sun, Oct 1, 2023, at 22:09, Scott Deboy wrote:
> 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.
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,
On Sun, Oct 1, 2023, at 21:28, Scott Deboy wrote:
> The ability to route events to tabs is a core feature in the code -
> that's how Chainsaw log messages end up in a Chainsaw-specific tab -
> but the ability to control that routing via a 'routing expression' w
The ability to route events to tabs is a core feature in the code -
that's how Chainsaw log messages end up in a Chainsaw-specific tab -
but the ability to control that routing via a 'routing expression' was
nuked from app-wide preferences - another thing we should bring back.
I
ady upgraded some dependencies that have security flaws. 2
> more
> >> are in the pom, but they have no patched versions so far.
> >>
> >> Should we add at least one feature? Is there maybe one already in that I
> >> missed?
> >>
> >> I would appreciate it if one of the more experienced Swing-devs here
> could
> >> advise or maybe contribute some code so we can justify a release.
> >>
> >> The next question would be:
> >> How is chainsaw released at all?
> >>
> >> Kind regards,
> >> Christian
> >>
>
We lost the initial 'Load Chainsaw Configuration' dialog (and menu
item) that gave folks a way to set up a Chainsaw configuration. I'd
like to see us restore that functionality, along with a menu support.
Right now, you have to define a receiver by hand, and it has to be
redefi
have no patched versions so far.
>>
>> Should we add at least one feature? Is there maybe one already in that I
>> missed?
>>
>> I would appreciate it if one of the more experienced Swing-devs here could
>> advise or maybe contribute some code so we can justify a release.
>>
>> The next question would be:
>> How is chainsaw released at all?
>>
>> Kind regards,
>> Christian
>>
o far.
>
> Should we add at least one feature? Is there maybe one already in that I
> missed?
>
> I would appreciate it if one of the more experienced Swing-devs here could
> advise or maybe contribute some code so we can justify a release.
>
> The next question would be:
> How is chainsaw released at all?
>
> Kind regards,
> Christian
>
ne of the more experienced Swing-devs here could
advise or maybe contribute some code so we can justify a release.
The next question would be:
How is chainsaw released at all?
Kind regards,
Christian
I would support https://github.com/apache/chainsaw being a set of standard go
libraries much like commons is for java.
Thoughts?
-Rob
> On Sep 26, 2023, at 6:08 PM, Rob Tompkins wrote:
>
> Ah :-)
>
> Cheers,
> -Rob
>
>> On Sep 26, 2023, at 6:03 PM, Robert Middl
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
a vote. Even
>> when we consider it dormant, we should consider to fix the problem.
>> Unlike log4j1, chainsaw was never considered EOL.
>>
>> I would like to hear from Scott but also Robert, who did the last commits.
>
> I was just reading that message again, and
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 'ch
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
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.
>
&
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?
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 fi
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"));
>
xception/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 o
te:
> 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:
>
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
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
be retired and until he positively says he will no
>> longer maintain it I am not willing to override that.
>
>
> Agreed. I don’t think this discussion is already due for a vote. Even
> when we consider it dormant, we should consider to fix the problem.
> Unlike log4j1, chai
On Thu, Sep 21, 2023 at 7:00 PM Volkan Yazıcı wrote:
>
> As earlier discussions[1] indicate, Chainsaw has been lacking on
> maintenance and no PMC member stepped up to perform necessary chores.
> This is a vote to retire the Chainsaw by means of
>
> - Move it to the list of
t 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
> >> ma
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 to perform necessary chores.
>> This is a vote to retire the Chainsaw by means of
>>
>> - Move it to the list of dormant
ultiple hosts into a single tab and
> filter in that view.
>
> Scott
>
>
>
> On Fri, Sep 22, 2023, 7:35 PM Robert Middleton
> wrote:
>
> > I think Chainsaw /can/ be useful, but it currently is not. If people are
> > willing to work on it a bit more, I can help ou
Ah :-)
Cheers,
-Rob
> On Sep 26, 2023, at 6:03 PM, Robert Middleton wrote:
>
> logging-chainsaw is not archived and contains the most up-to-date code.
> The old 'chainsaw' repository has been archived.
>
> -Robert Middleton
>
> On Tue, Sep 26, 2023 at 5:57 P
logging-chainsaw is not archived and contains the most up-to-date code.
The old 'chainsaw' repository has been archived.
-Robert Middleton
On Tue, Sep 26, 2023 at 5:57 PM Rob Tompkins wrote:
> Maybe we should un-archive it and run with it in a new direction?
>
> -Rob
>
&
Maybe we should un-archive it and run with it in a new direction?
-Rob
> On Sep 26, 2023, at 4:43 PM, Christian Grobmeier wrote:
>
> Hi,
>
> Infra archived this repo for us:
> https://github.com/apache/chainsaw
>
> Kind regards,
> Christian
>
> On Fri, Sep
Hi,
Infra archived this repo for us:
https://github.com/apache/chainsaw
Kind regards,
Christian
On Fri, Sep 22, 2023, at 22:33, Gary Gregory wrote:
> On Fri, Sep 22, 2023 at 2:28 PM Christian Grobmeier
> wrote:
>>
>>
>>
>> On Fri, Sep 22, 2023, at 20:16, Gary Gre
ork properly. I
>>> think it's good and needed, but it definitely needs a user-friendly way of
>>> selecting a log file and viewing a live example of how it will parse the
>>> log file. Although for my purposes, we don't actually write to a log file,
>>>
ded, but it definitely needs a user-friendly way of
>> selecting a log file and viewing a live example of how it will parse the
>> log file. Although for my purposes, we don't actually write to a log file,
>> so it's a bit of a moot point.
>>
>> The next quest
urposes, we don't actually write to a log file,
> so it's a bit of a moot point.
>
> The next question of course is what do I feel would be better? I spent
> some time working on that tonight as a proof of concept, and here's what I
> came up with(with chainsaw in the ba
a log file,
so it's a bit of a moot point.
The next question of course is what do I feel would be better? I spent
some time working on that tonight as a proof of concept, and here's what I
came up with(with chainsaw in the background for reference):
[image: Screenshot from 2023-09-25 2
that he would help with maintenance and Rob T has also
> indicated that he would perhaps help, this is my view of the current status
> of Chainsaw and what I feel its current deficiencies are.
>
> Current status: Master builds and mostly works. The last thing that I had
> been work
Since Scott has said that he would help with maintenance and Rob T has also
indicated that he would perhaps help, this is my view of the current status
of Chainsaw and what I feel its current deficiencies are.
Current status: Master builds and mostly works. The last thing that I had
been working
ink Chainsaw /can/ be useful, but it currently is not. If people are
> willing to work on it a bit more, I can help out a bit. I can see it
> potentially being useful for the type of work that I do(embedded work) but
> it needs a fair amount of attention in order to get to the useful level
I think Chainsaw /can/ be useful, but it currently is not. If people are
willing to work on it a bit more, I can help out a bit. I can see it
potentially being useful for the type of work that I do(embedded work) but
it needs a fair amount of attention in order to get to the useful level IMO.
I
2023, at 21:53, Robert Middleton wrote:
> >> > I think #1 is a mirror of SVN(
> >> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a
> >> > mirror of the gitbox repository.
> >>
> >> Looks like the SVN mirror is outdated. Can
What version of Java are you using here? Chances are that you’ll need to use
Java 8 for this.
> On Sep 22, 2023, at 1:34 PM, Christian Grobmeier wrote:
>
> Hi,
>
> I tried to start Chainsaw from the official build, using Maven (mvn package)
> and even starting it using th
oes not work? [1] hasn't been updated since
> 2014.
>
> [1] https://github.com/apache/chainsaw
> [2] https://github.com/apache/logging-chainsaw
Hi,
I tried to start Chainsaw from the official build, using Maven (mvn package)
and even starting it using the LogUI main class.
All methods failed for various reasons.
What is the best method to get Chainsaw started, when trying to fix an issue?
Kind regards,
Christian
When running using
gt; Gary
>
> On Fri, Sep 22, 2023, 1:50 PM Christian Grobmeier wrote:
>
>>
>> On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote:
>> > I think #1 is a mirror of SVN(
>> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a
>>
N(
> > https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a
> > mirror of the gitbox repository.
>
> Looks like the SVN mirror is outdated. Can we safely remove it?
> If there are no objections, I will create a ticket with infra
>
> Christian
>
> >
On Thu, Sep 21, 2023, at 21:53, Robert Middleton wrote:
> I think #1 is a mirror of SVN(
> https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a
> mirror of the gitbox repository.
Looks like the SVN mirror is outdated. Can we safely remove it?
If there are no obje
-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
it I am not willing to override that.
Agreed. I don’t think this discussion is already due for a vote. Even when we
consider it dormant, we should consider to fix the problem. Unlike log4j1,
chainsaw was never considered EOL.
I would like to hear from Scott but also Robert, who did the
1 - 100 of 375 matches
Mail list logo
