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

I'm also digging the DSL they have far better than the XML-like thing that JavaFX uses normally. On 10 November 2017 at 23:12, Remko Popma wrote: > TornadoFX looks very interesting! Thanks for the link! > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Nov 11, 2

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

TornadoFX looks very interesting! Thanks for the link! (Shameless plug) Every java main() method deserves http://picocli.info > On Nov 11, 2017, at 13:24, Matt Sicker wrote: > > Using Kotlin could also attract Android developers who were otherwise stuck > using Java 6 for years. > > As mention

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

IIRC, the easiest way to support it might be to use https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/spi/AbstractLoggerAdapter.html On 10 November 2017 at 22:16, Gary Gregory wrote: > I think you are correct... > > Gary > > On Fri, Nov 10, 2017 at 6:59 PM, Matt Sic

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

Using Kotlin could also attract Android developers who were otherwise stuck using Java 6 for years. As mentioned in an earlier reply, this framework could be useful for Kotlin/JavaFX: On 10 November 2017 at 22:12, Remko Popma wrote: > Now that I think of it,

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

I think you are correct... Gary On Fri, Nov 10, 2017 at 6:59 PM, Matt Sicker wrote: > Wouldn't this implementation contain incorrect caller location information? > > On 10 November 2017 at 19:25, wrote: > > > Repository: logging-log4j2 > > Updated Branches: > > refs/heads/master aad2f132b ->

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

Now that I think of it, all else being equal, the combination of Kotlin and JavaFX may be attractive to get other new developers interested and grow the community... (Shameless plug) Every java main() method deserves http://picocli.info > On Nov 11, 2017, at 10:58, Matt Sicker wrote: > > Cons

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

Wouldn't this implementation contain incorrect caller location information? On 10 November 2017 at 19:25, wrote: > Repository: logging-log4j2 > Updated Branches: > refs/heads/master aad2f132b -> 7d52f131e > > > [LOG4J2-2114] Provide a native Log4j 2 implementation of Eclipse Jetty's > org.ecli

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

Considering it takes about 2-3 months of daily use of Scala to get comfortable, perhaps Kotlin would be a better choice. It's a simpler language and is supposed to be easy for Java developers to pick up. On 10 November 2017 at 19:43, Remko Popma wrote: > I don’t know either language but I’d be m

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

I don’t know either language but I’d be more interested in learning Kotlin than learning Scala. OTOH I’m not sure how much time I’ll be able to contribute to Chainsaw so not sure how much that should count for. (Shameless plug) Every java main() method deserves http://picocli.info > On Nov 1

Re: [PROPOSAL] New module log4j-jetty

On Thu, Nov 9, 2017 at 3:33 PM, Gary Gregory wrote: > On Thu, Nov 9, 2017 at 3:32 PM, Ralph Goers > wrote: > >> >> > On Nov 9, 2017, at 2:34 PM, Gary Gregory >> wrote: >> > >> > On Thu, Nov 9, 2017 at 1:49 PM, Ralph Goers > > >> > wrote: >> > >> >> Every module equates to another jar. I just do

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

That's what I hear. I don't know Kotlin, but I'd certainly be interested in learning! (particularly so I can write Gradle builds in a statically typed language) On 10 November 2017 at 19:10, Gary Gregory wrote: > I think Kotlin would be more approachable than Scala... thoughts? > > Gary > > On F

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

I think Kotlin would be more approachable than Scala... thoughts? Gary On Fri, Nov 10, 2017 at 3:26 PM, Matt Sicker wrote: > On 10 November 2017 at 16:17, Robert Middleton > wrote: > > > What would the advantage be of using Scala vs just normal Java? > > Mostly from a curiosity standpoint; I'v

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

On 10 November 2017 at 16:17, Robert Middleton wrote: > What would the advantage be of using Scala vs just normal Java? > Mostly from a curiosity standpoint; I've never done Scala so I don't > know it works. > The main advantage I can see is that most of the developers interested in working on v

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

What would the advantage be of using Scala vs just normal Java? Mostly from a curiosity standpoint; I've never done Scala so I don't know it works. Did you actually have trouble building? I'm pretty sure that when I built it a few months ago I simply opened up the project in Netbeans and it built

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I can certainly update the screenshot for the site, though if it's embedded in the bin archive, then that won't get updated. Thanks for verifying! On 10 November 2017 at 14:43, Scott Deboy wrote: > Here's my +1. > > Site looks good, and it builds and runs. > > Thanks Matt > > On 11/10/17, Scott

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Here's my +1. Site looks good, and it builds and runs. Thanks Matt On 11/10/17, Scott Deboy wrote: > Updated screenshot. > > On 11/10/17, Scott Deboy wrote: >> Awesome..I'll commit a new screenshot then. >> >> On 11/10/17, Ralph Goers wrote: >>> The web site doesn’t have to be locked into the

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Updated screenshot. On 11/10/17, Scott Deboy wrote: > Awesome..I'll commit a new screenshot then. > > On 11/10/17, Ralph Goers wrote: >> The web site doesn’t have to be locked into the release. An image can be >> updated after the release pretty easily. >> >> Ralph >> >> >>> On Nov 10, 2017, at

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Awesome..I'll commit a new screenshot then. On 11/10/17, Ralph Goers wrote: > The web site doesn’t have to be locked into the release. An image can be > updated after the release pretty easily. > > Ralph > > >> On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote: >> >> Would it be possible for me to

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

The web site doesn’t have to be locked into the release. An image can be updated after the release pretty easily. Ralph > On Nov 10, 2017, at 1:03 PM, Scott Deboy wrote: > > Would it be possible for me to push an updated screenshot and re-spin? > > On 11/10/17, Scott Deboy wrote: >> Wow th

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Would it be possible for me to push an updated screenshot and re-spin? On 11/10/17, Scott Deboy wrote: > Wow that screen shot looks ancient and ugly. I should pull up > something on the Mac with updated default colors - it looks much > better. > > Scott > > On 11/10/17, Matt Sicker wrote: >> Oh

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Wow that screen shot looks ancient and ugly. I should pull up something on the Mac with updated default colors - it looks much better. Scott On 11/10/17, Matt Sicker wrote: > Oh, and in case it isn't obvious how to test this, you can extract from > either the zip or tar.gz files and run the cha

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Oh, and in case it isn't obvious how to test this, you can extract from either the zip or tar.gz files and run the chainsaw script in bin/ corresponding to your operating system. Note that this crashes when using Java 9 for some reason, so make sure to use Java 6, 7, or 8. I built this using Java

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

Release candidate available. Based on my experiences here, I think one of the first useful things to do for 3.x would be to overhaul the build system. Since it seems like Scala may be the desired language to write this in, I may experiment with using SBT for the build instead of Maven+Ant. On 16 O

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

Quick note: using the maven-release-plugin doesn't seem to work in this project. Also, sources and documentation are included in the bin.* files while the standalone.* files are just the jars and startup scripts. On 10 November 2017 at 13:00, Matt Sicker wrote: > This is a vote to release Apache

[VOTE] Release Apache Chainsaw 2.0.0-rc1

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: https://dist.apache.org/repos/dist/dev/logging/chainsaw/ svn revision 23048 Site: http://musigm

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

Please review this commit as I want to make sure I didn’t make any mistakes. Ralph > On Nov 10, 2017, at 6:46 AM, rgo...@apache.org wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 0dca987fc -> aad2f132b > > > LOG4J2-2106 Reduce locking when checking for rollover