I’m wondering if in part Chainsaw died because of the ELK stack?
Ron DiFrango
On 4/9/17, 3:56 AM, "Robert Lu" <robberp...@gmail.com> wrote:
Hi, all.
I think developer need a tool to view, search log. Chainsaw was a great
tool, but need update.
I want to contribute to Chainsaw.
On Sat, Apr 8, 2017 at 10:25 AM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:
> Brett and Robert, are you suggesting you would want to get involved in
> improving Chainsaw if it moved to git?
>
> Ralph
>
> > On Apr 7, 2017, at 6:42 PM, Brett Randall <javabr...@gmail.com> wrote:
> >
> > +1 for migration to Git.
> >
> > On 6 April 2017 at 07:44, Matt Sicker <boa...@gmail.com> wrote:
> >
> >> We can probably do that, though usually we like to do a 72 hour grace
> >> period to make sure there are no objections before migrating
> repositories.
> >>
> >> On 6 April 2017 at 02:01, Robert Lu <robberp...@gmail.com> wrote:
> >>
> >>> Can chainsaw migrate to git?
> >>>
> >>> On Thu, Mar 30, 2017 at 4:04 AM, Matt Sicker <boa...@gmail.com> wrote:
> >>>
> >>>> You need to use the new home.apache.org site for uploading things now
> >>>> anyways. Who knows how long they'll keep the old server online. If we
> >> set
> >>>> it up in Jenkins, we can also have snapshots published to Nexus.
> >>>>
> >>>> On 29 March 2017 at 14:53, Ralph Goers <ralph.go...@dslextreme.com>
> >>> wrote:
> >>>>
> >>>>> We can’t be pointing people to use snapshots from your personal
page.
> >>> I’m
> >>>>> not even sure how you can publish there any more. Can’t you do a
> >>> release
> >>>>> if there are features that you use? It would be nice to at least
say
> >>> it
> >>>>> supports Log4j 2 and how to set it up.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Mar 29, 2017, at 12:30 PM, Scott Deboy <scott.de...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>> I use it and it works well for logs under 1M records, assuming you
> >>> can
> >>>>>> give the JVM enough memory.
> >>>>>>
> >>>>>> I use the developer snapshot here:
> >>>>>>
> >>>>>> https://people.apache.org/~sdeboy/
> >>>>>>
> >>>>>>
> >>>>>> On 3/29/17, João Ferreira <ferreirinha...@hotmail.com> wrote:
> >>>>>>> Yeah, that was what i expected. But is there any project replacing
> >>>> this
> >>>>>>> one?
> >>>>>>>
> >>>>>>> Wednesday, 29 March 2017, 08:01PM +01:00 from Igal @ Lucee.org
> >>>>>>> i...@lucee.org<mailto:i...@lucee.org>:
> >>>>>>>
> >>>>>>> https://logging.apache.org/chainsaw/changes-report.html
> >>>>>>> Last Published: 09/01/2007
> >>>>>>>
> >>>>>>> I'd say it's not active.
> >>>>>>>
> >>>>>>> Igal Sapir
> >>>>>>> Lucee Core Developer
> >>>>>>> Lucee.org <http://lucee.org/>
> >>>>>>>
> >>>>>>> On 3/29/2017 11:56 AM, João Ferreira wrote:
> >>>>>>>> Hello,
> >>>>>>>>
> >>>>>>>> Is apache chainsaw still an active project? If not, was it
> >> replaced
> >>>> by
> >>>>>>>> another project?
> >>>>>>>>
> >>>>>>>> Best regards
> >>>>>>>> Joao
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>> ------------------------------------------------------------
> >>> ---------
> >>>>>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> >>>>>> For additional commands, e-mail: log4j-user-help@logging.
> >> apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------
> >> ---------
> >>>>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> >>>>> For additional commands, e-mail: log4j-user-h...@logging.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> Matt Sicker <boa...@gmail.com>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Robert Lu <robberp...@gmail.com>
> >>> About me: http://about.me/RobberPhex
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker <boa...@gmail.com>
> >>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
>
--
Robert Lu <robberp...@gmail.com>
About me: http://about.me/RobberPhex
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to
Capital One and/or its affiliates and may only be used solely in performance of
work or services for Capital One. The information transmitted herewith is
intended only for use by the individual or entity to which it is addressed. If
the reader of this message is not the intended recipient, you are hereby
notified that any review, retransmission, dissemination, distribution, copying
or other use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error, please
contact the sender and delete the material from your computer.
