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

So to summarize Qt would lead to shoe horning in all the things that are simple to do and constantly being improved and optimized with Angular or ReactJS and most of the use cases I mentioned are not supported. Quality > quantity True but you have a really good quality indicator in the number

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

It feels to me that this whole topic has gotten side-tracked. I think you first need to decide what you want to build before you decide on technologies. Are you building a web application or a desktop? Of course, there might be technology that lets you do both, to some degree. As far as I

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

If you'd like to contribute a proof of concept, that would be great! I'm not a fan of frontend web development anymore Given how much variation there has been in package formats etc. (UMD, AMD, CommonJS, God help us D, etc) I don't blame you.  Just AOT compile, Babelify it, then rollupJS it,

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

On 12 November 2017 at 21:26, Ole Ersoy wrote: > Dude Seriously??? ... Even if you can the developer pool for that is > a tiny fraction of what you get with a modern web application > architecture. Which organizations are investing in Qt? > KDE for one. > - Can you

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

On 11/12/2017 07:23 PM, Matt Sicker wrote: On 12 November 2017 at 13:52, Ole Ersoy wrote: With a progressive Angularjs Webapp it will be a realtime / offline / cached and web deployable analysis tool. You can deploy it to browsers, your phone, the desktop. The browser

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

With regard to the Qt idea, while that's certainly possible I don't really see the need to go that route, as it would (still) be a complete re-write at that point. While it's true that Qt does have scripting in it(QML, which is essentially JavaScript), I'm not quite sure how that solves problems.

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

On 12 November 2017 at 20:10, Ole Ersoy wrote: > If you use it with PouchDB, localStorage, or session storage then it's a > NoSQL database. PouchDB also features sync replication with CouchDB. > I was thinking more like the uses I've seen where ES was used in place of

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

ES is pretty simple to use. It has a lot of neat features for text searching as well. That doesn't stop people from pretending it's a NoSQL database, however. If you use it with PouchDB, localStorage, or session storage then it's a NoSQL database.  PouchDB also features sync replication with

Re: Jenkins build is still unstable: Log4j 2.x #3170

https://github.com/apache/logging-log4j2/search?utf8=%E2%9C%93=hadoop.log= I see at least one test that's trying to use the java.io.tmpdir for said file. The only reason why a file named /tmp/hadoop.log couldn't be created would be because it already exists and is owned by a different user on the

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

On 12 November 2017 at 14:26, Ole Ersoy wrote: > I tend to look at code as just a blueprint proven blueprint / good set of > guidelines for how to implement something. There's potentially a bit of boilerplate or heavy lifting we can utilize from the existing Chainsaw

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I don't recall why - it was a while back :) Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory issue. On 11/12/17, Matt Sicker wrote: > On 12 November 2017 at 13:53, Scott Deboy wrote: > >> That's right -forgot we rev'd to 2.1

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

On 12 November 2017 at 13:52, Ole Ersoy wrote: > With a progressive Angularjs Webapp it will be a realtime / offline / > cached and web deployable analysis tool. You can deploy it to browsers, > your phone, the desktop. The browser can cache assets such that the app is >

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

On 12 November 2017 at 13:42, Scott Deboy wrote: > I'm playing with the high-level ES Java APIs now to see how easy it > will be to create a new Receiver that allows Chainsaw to query Elastic > Search directly. > > It looks like it'll be pretty simple. > ES is pretty

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

On 12 November 2017 at 13:53, Scott Deboy wrote: > That's right -forgot we rev'd to 2.1 internally (info.plist, release > notes, couple other places). > Any particular reason? > Would it be easiest to release the new version as 2.1.0.0 instead of > 2.0.0-rc1? Otherwise

Re: Jenkins build is still unstable: Log4j 2.x #3170

I am not sure why this is suddenly failing with a permission denied trying to create /tmp/hadoop.log. But why is it trying to create a file there instead of under the target directory? Ralph > On Nov 12, 2017, at 2:39 PM, Apache Jenkins Server > wrote: > > See >

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

I haven't had a chance to dive into the code yet, but I'd imagine that there may be some sort of boundary in place (or can be put in place) between the UI and the logic such that multiple UIs can reuse the same code. That sort of pattern is not specific to web development. :) One of the

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

On 11/12/2017 07:24 AM, Mikael Ståldal wrote: On 2017-11-12 00:57, Ole Ersoy wrote: > A chainsaw implementation in Electron would provide a better developer > and user experience I would think though But that would require a complete rewrite of the app, with no opportunity to reuse any of the

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

When starting Chainsaw, I see this warning in the log: menu 'Connect to' was NOT added because the 'Help' menu could not be located There is a "Connect to" menu though, and the "Learn more about ZeroConf" works. On 2017-11-10 20:00, Matt Sicker wrote: This is a vote to release Apache

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

That's right -forgot we rev'd to 2.1 internally (info.plist, release notes, couple other places). Would it be easiest to release the new version as 2.1.0.0 instead of 2.0.0-rc1? Otherwise I could downgrade 2.1 refs, we never had an official release with that rev. Scott On 11/12/17, Mikael

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

Dashboard/visualization support would be awesome, but this is both a real time as well as offline analysis tool. Cursor-style previous/next page event rendering would make it a terrible user experience IMO. With a progressive Angularjs Webapp it will be a realtime / offline / cached and web

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I think we can either fix or remove that menu item from the menu after the release - I don't know how useful it is. Scott On 11/12/17, Mikael Ståldal wrote: > When starting Chainsaw, I see this warning: > > Could not find any local JavaDocs, you might want to consider running

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Would be nice to be able to load that as a plugin in a more dynamic fashion. But we can keep that for a future version, not blocking this release. On 2017-11-12 20:45, Scott Deboy wrote: That's right - we don't bundle in a JMS jar, although users can add one to the classpath to use the

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Fixed. On 11/12/17, Mikael Ståldal wrote: > In the About text, it says: > > Please send questions, bug reports and/or feature requests to > log4j-...@logging.apache.org > > which is obsolete. > > > On 2017-11-10 20:00, Matt Sicker wrote: >> This is a vote to release Apache

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

I see a use case for a stand-alone log viewer/analyzer application which doesn't require any heavy infrastructure like ElasticSearch. I would like Chainsaw to focus on that use case. On 2017-11-12 05:22, Ole Ersoy wrote: I had a brief peek.  My first impression was that the whole thing needs

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

That's right - we don't bundle in a JMS jar, although users can add one to the classpath to use the JMSReceiver. On 11/12/17, Mikael Ståldal wrote: > When running Chainsaw, I see this error message: > > Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks >

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

In release notes in the app, it says version 2.1. On 2017-11-10 20:00, Matt Sicker wrote: This is a vote to release Apache Chainsaw 2.0.0-rc1. (Note: I've created release instructions on the new wiki: < https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>) Artifacts:

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

I'm playing with the high-level ES Java APIs now to see how easy it will be to create a new Receiver that allows Chainsaw to query Elastic Search directly. It looks like it'll be pretty simple. Scott On 11/12/17, Matt Sicker wrote: > I'm heavily opposed to myself being

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

When starting Chainsaw, I see this warning: Could not find any local JavaDocs, you might want to consider running 'ant javadoc'. The release version will be able to access Javadocs from the Apache website. And accessing Javadocs from the Help menu does not work. On 2017-11-10 20:00, Matt

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

In the About text, it says: Please send questions, bug reports and/or feature requests to log4j-...@logging.apache.org which is obsolete. On 2017-11-10 20:00, Matt Sicker wrote: This is a vote to release Apache Chainsaw 2.0.0-rc1. (Note: I've created release instructions on the new wiki: <

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

When running Chainsaw, I see this error message: Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks like a dependent class is missing from the classpath java.lang.NoClassDefFoundError: javax/jms/MessageListener It seems to work anyway (without JMX support I suppose)

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

I'm heavily opposed to myself being involved in any non-trivial web UI code until some semblance of sanity arises in that space (see for example the Elm programming language which does a good job toward accomplishing some of that). Electron, while a cool piece of technology, is not my ideal way to

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

The apache-chainsaw-2.0.0-standalone.tar.gz artifact has wrong permissions set on the bin directory: $ tar -tvzf apache-chainsaw-2.0.0-standalone.tar.gz d- 0/0 0 2017-11-10 19:24 apache-chainsaw/2.0.0/bin/ after extracting: $ cd apache-chainsaw-2.0.0/ $ ls bin repo $ cd bin/

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

On 2017-11-12 16:00, Gary Gregory wrote: On Sun, Nov 12, 2017 at 7:25 AM, Mikael Ståldal wrote: Do we want a package-info.java in the Jetty package, like in the Tomcat package? And you should probably add a section about Jetty integraion in

Re: logging-log4j2 git commit: LOG4J2-2106 Reduce locking when checking for rollover

I reviewed the changes and found some potential issues. Please see my comment on https://issues.apache.org/jira/browse/LOG4J2-2106 On Sun, Nov 12, 2017 at 6:17 AM, Daan Hoogland wrote: > Thanks, I'm trying the commitish build install use. > > Sent from Nine

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

On Sun, Nov 12, 2017 at 7:25 AM, Mikael Ståldal wrote: > Do we want a package-info.java in the Jetty package, like in the Tomcat > package? > > And you should probably add a section about Jetty integraion in > log4j-appserver/src/site/markdown/index.md.vm Done. Please review.

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

Having said that, I don't mean that Ole Ersoy's idea is inherently bad. But it should be a new independent project (possibly in Apache Logging Services). On 2017-11-12 14:27, Mikael Ståldal wrote: To me, that sound like transforming it into something completely different, and a use case

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

On Nov 12, 2017 06:24, "Mikael Ståldal" wrote: On 2017-11-12 00:57, Ole Ersoy wrote: > A chainsaw implementation in Electron would provide a better developer > and user experience I would think though But that would require a complete rewrite of the app, with no opportunity to

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

On Nov 12, 2017 06:27, "Mikael Ståldal" wrote: To me, that sound like transforming it into something completely different, and a use case which there already exists quite some other tools for already. Shouldn't we keep Chainsaw as a stand-alone desktop UI app? +1 Gary

Re: logging-log4j2 git commit: [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's org.eclipse.jetty.util.log.Logger.

Do we want a package-info.java in the Jetty package, like in the Tomcat package? And you should probably add a section about Jetty integraion in log4j-appserver/src/site/markdown/index.md.vm On 2017-11-11 23:43, Gary Gregory wrote: Please code review git master. I'm not sure I have the class

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

To me, that sound like transforming it into something completely different, and a use case which there already exists quite some other tools for already. Shouldn't we keep Chainsaw as a stand-alone desktop UI app? On 2017-11-12 05:22, Ole Ersoy wrote: I had a brief peek.  My first impression

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

On 2017-11-12 00:57, Ole Ersoy wrote: > A chainsaw implementation in Electron would provide a better developer > and user experience I would think though But that would require a complete rewrite of the app, with no opportunity to reuse any of the existing Java code. Both Scala and Kotlin