Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

I finally looked at this. I pushed a change to app assembler config to make the bin directory executable, and updated HOWTOBUILD to mention you need to run mvn site:site first. Can we resin? On 11/13/17, Matt Sicker wrote: > Another thing I noticed is that the downloads page

Re: logging-log4j2 git commit: [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2.

JUnit 5 might have something more extensible there, though it does require Java 8 (at least for the test artifacts). I'm not sure either as I've mostly been using other testing frameworks when not using JUnit 4. On 19 January 2018 at 21:19, Remko Popma wrote: > Reducing

Re: logging-log4j2 git commit: [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2.

Reducing the time it takes to run the core tests is key. It would be great if we could specify which tests should be forked, and run the rest non-forked. Perhaps we need to enhance Surefire. Or can JUnit 5 help somehow (haven’t looked at it yet)? Remko (Shameless plug) Every java main()

[log4cxx] Current State

As prompted by the discussion last week about the state of log4cxx, is there a current blocker(apart from Thorsten's time) halting a release of log4cxx/regular maintenance? I would like to help out on the project to do a release / add new features, but I'm not sure what the best way to go about

Re: logging-log4j2 git commit: [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2.

I'd much prefer if we had a leaner core repo for more frequent releases (RERO after all). I've only done the release process a couple times, but Ralph is right: more modules means a larger pain in the ass. The other thing we could really benefit from would be speeding up unit tests. If we can run