date:20180119

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

2018-01-19 Thread Scott Deboy

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 needs to be updated to
> link to the (future) dist URLs instead of ones in the site's directory (no
> proper mirroring in the old links).
>
> On 12 November 2017 at 19:25, Scott Deboy  wrote:
>
>> 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 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 I could downgrade 2.1 refs, we never had an
>> >> official release with that rev.
>> >>
>> >
>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no
>> tags
>> > or releases for any 2.x release at all, so it seemed like a logical
>> > starting point.
>> >
>> > And thanks for testing! We should be able to clean up for a proper 2.x
>> > release. :)
>> >
>> > --
>> > Matt Sicker 
>> >
>>
>
>
>
> --
> Matt Sicker 
>

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

2018-01-19 Thread Matt Sicker

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 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() method deserves http://picocli.info
>
> > On Jan 20, 2018, at 8:21, Matt Sicker  wrote:
> >
> > 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 them without forking, I think that would help a lot in execution
> > speedups. I'm not sure if using Gradle or something else instead of Maven
> > would speed things up there, but I believe there are more low hanging
> fruit
> > we could handle before something that drastic.
> >
> >> On 18 January 2018 at 23:31, Ralph Goers 
> wrote:
> >>
> >> Gary, I am complaining because I perform the releases. You never have.
> We
> >> keep adding more and more crap to the build and it keeps taking longer
> and
> >> longer. Af far as I am concerned that is a valid technical reason.
> >>
> >> My -1 stands.
> >>
> >> Ralph
> >>
> >>
> >>> On Jan 18, 2018, at 10:24 PM, Gary Gregory 
> >> wrote:
> >>>
> >>> On Thu, Jan 18, 2018 at 10:20 PM, Ralph Goers <
> >> ralph.go...@dslextreme.com>
> >>> wrote:
> >>>
>  OK, but that doesn’t resolve the initial problem. The log4j 2 project
> is
>  too large.
> 
> >>>
> >>> From what I've experienced, folks complain about the size of the api
> and
> >>> core jars, not the Maven project.
> >>>
> >>> What is the target size/metric if it is currently "too large"? ;-)
> >>>
> >>> Gary
> >>>
> >>>
>  Ralph
> 
> > On Jan 18, 2018, at 10:15 PM, Gary Gregory 
>  wrote:
> >
> > On Thu, Jan 18, 2018 at 9:43 PM, Ralph Goers <
> >> ralph.go...@dslextreme.com
> >
> > wrote:
> >
> >> In addition, the build is now failing to compile on Jenkins.
> >>
> >
> > Oops, please accept my apologies. I got caught by the Eclipse
> compiler
> > being more forgiving (or more powerful) than the Oracle compiler in
> the
> > generics department. All of that despite the Maven partial builds I
> >> ran.
>  I
> > must have not run the clean goal or some-such.
> >
> > Gary
> >
> >
> >> Ralph
> >>
> >>> On Jan 18, 2018, at 9:28 PM, Ralph Goers <
> ralph.go...@dslextreme.com
> >>>
> >> wrote:
> >>>
> >>> -1
> >>>
> >>> Please revert and move this to the log4j plugins project.
> >>>
> >>> Ralph
> >>>
>  On Jan 18, 2018, at 8:54 PM, ggreg...@apache.org wrote:
> 
>  Repository: logging-log4j2
>  Updated Branches:
>  refs/heads/master bb6fcd09e -> 639f093b8
> 
> 
>  [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling
>  through
>  Apache Commons DBCP 2.
> 
>  Project: http://git-wip-us.apache.org/
> repos/asf/logging-log4j2/repo
>  Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
> >> commit/639f093b
>  Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/
> >> 639f093b
>  Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/
> >> 639f093b
> 
>  Branch: refs/heads/master
>  Commit: 639f093b8103df2c2eda8d62fd12d7619d98ac04
>  Parents: bb6fcd0
>  Author: Gary Gregory 
>  Authored: Thu Jan 18 20:54:47 2018 -0700
>  Committer: Gary Gregory 
>  Committed: Thu Jan 18 20:54:47 2018 -0700
> 
>  
>  --
>  log4j-jdbc-dbcp2/pom.xml| 170
> >> +++
>  .../db/jdbc/PoolingDriverConnectionSource.java  | 155
>  +
>  log4j-jdbc-dbcp2/src/site/manual/index.md   |  35 
>  log4j-jdbc-dbcp2/src/site/site.xml  |  52 ++
>  .../jdbc/PoolingDriverConnectionSourceTest.java |  96 +++
>  pom.xml |   1 +
>  src/changes/changes.xml |   3 +
>  src/site/xdoc/manual/appenders.xml  |  28 ++-
>  8 files changed, 537 insertions(+), 3

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

2018-01-19 Thread Remko Popma

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() method deserves http://picocli.info

> On Jan 20, 2018, at 8:21, Matt Sicker  wrote:
> 
> 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 them without forking, I think that would help a lot in execution
> speedups. I'm not sure if using Gradle or something else instead of Maven
> would speed things up there, but I believe there are more low hanging fruit
> we could handle before something that drastic.
> 
>> On 18 January 2018 at 23:31, Ralph Goers  wrote:
>> 
>> Gary, I am complaining because I perform the releases. You never have. We
>> keep adding more and more crap to the build and it keeps taking longer and
>> longer. Af far as I am concerned that is a valid technical reason.
>> 
>> My -1 stands.
>> 
>> Ralph
>> 
>> 
>>> On Jan 18, 2018, at 10:24 PM, Gary Gregory 
>> wrote:
>>> 
>>> On Thu, Jan 18, 2018 at 10:20 PM, Ralph Goers <
>> ralph.go...@dslextreme.com>
>>> wrote:
>>> 
 OK, but that doesn’t resolve the initial problem. The log4j 2 project is
 too large.
 
>>> 
>>> From what I've experienced, folks complain about the size of the api and
>>> core jars, not the Maven project.
>>> 
>>> What is the target size/metric if it is currently "too large"? ;-)
>>> 
>>> Gary
>>> 
>>> 
 Ralph
 
> On Jan 18, 2018, at 10:15 PM, Gary Gregory 
 wrote:
> 
> On Thu, Jan 18, 2018 at 9:43 PM, Ralph Goers <
>> ralph.go...@dslextreme.com
> 
> wrote:
> 
>> In addition, the build is now failing to compile on Jenkins.
>> 
> 
> Oops, please accept my apologies. I got caught by the Eclipse compiler
> being more forgiving (or more powerful) than the Oracle compiler in the
> generics department. All of that despite the Maven partial builds I
>> ran.
 I
> must have not run the clean goal or some-such.
> 
> Gary
> 
> 
>> Ralph
>> 
>>> On Jan 18, 2018, at 9:28 PM, Ralph Goers >> 
>> wrote:
>>> 
>>> -1
>>> 
>>> Please revert and move this to the log4j plugins project.
>>> 
>>> Ralph
>>> 
 On Jan 18, 2018, at 8:54 PM, ggreg...@apache.org wrote:
 
 Repository: logging-log4j2
 Updated Branches:
 refs/heads/master bb6fcd09e -> 639f093b8
 
 
 [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling
 through
 Apache Commons DBCP 2.
 
 Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
 Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
>> commit/639f093b
 Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/
>> 639f093b
 Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/
>> 639f093b
 
 Branch: refs/heads/master
 Commit: 639f093b8103df2c2eda8d62fd12d7619d98ac04
 Parents: bb6fcd0
 Author: Gary Gregory 
 Authored: Thu Jan 18 20:54:47 2018 -0700
 Committer: Gary Gregory 
 Committed: Thu Jan 18 20:54:47 2018 -0700
 
 
 --
 log4j-jdbc-dbcp2/pom.xml| 170
>> +++
 .../db/jdbc/PoolingDriverConnectionSource.java  | 155
 +
 log4j-jdbc-dbcp2/src/site/manual/index.md   |  35 
 log4j-jdbc-dbcp2/src/site/site.xml  |  52 ++
 .../jdbc/PoolingDriverConnectionSourceTest.java |  96 +++
 pom.xml |   1 +
 src/changes/changes.xml |   3 +
 src/site/xdoc/manual/appenders.xml  |  28 ++-
 8 files changed, 537 insertions(+), 3 deletions(-)
 
 --
 
 
 http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
>> 639f093b/log4j-jdbc-dbcp2/pom.xml
 
 --
 diff --git a/log4j-jdbc-dbcp2/pom.xml b/log4j-jdbc-dbcp2/pom.xml
 new file mode 100644
 index 000..18e0e86
 --- /dev/null
 +++ b/log4j-jdbc-dbcp2/pom.xml

[log4cxx] Current State

2018-01-19 Thread Robert Middleton

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 this is, or even if my help is needed.

There are some place where I as a user of log4cxx would like to see it
go, but I don't want to spend the time to implement updates/new
features if they're not going to be used.

-Robert Middleton

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

2018-01-19 Thread Matt Sicker

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 them without forking, I think that would help a lot in execution
speedups. I'm not sure if using Gradle or something else instead of Maven
would speed things up there, but I believe there are more low hanging fruit
we could handle before something that drastic.

On 18 January 2018 at 23:31, Ralph Goers  wrote:

> Gary, I am complaining because I perform the releases. You never have. We
> keep adding more and more crap to the build and it keeps taking longer and
> longer. Af far as I am concerned that is a valid technical reason.
>
> My -1 stands.
>
> Ralph
>
>
> > On Jan 18, 2018, at 10:24 PM, Gary Gregory 
> wrote:
> >
> > On Thu, Jan 18, 2018 at 10:20 PM, Ralph Goers <
> ralph.go...@dslextreme.com>
> > wrote:
> >
> >> OK, but that doesn’t resolve the initial problem. The log4j 2 project is
> >> too large.
> >>
> >
> > From what I've experienced, folks complain about the size of the api and
> > core jars, not the Maven project.
> >
> > What is the target size/metric if it is currently "too large"? ;-)
> >
> > Gary
> >
> >
> >> Ralph
> >>
> >>> On Jan 18, 2018, at 10:15 PM, Gary Gregory 
> >> wrote:
> >>>
> >>> On Thu, Jan 18, 2018 at 9:43 PM, Ralph Goers <
> ralph.go...@dslextreme.com
> >>>
> >>> wrote:
> >>>
>  In addition, the build is now failing to compile on Jenkins.
> 
> >>>
> >>> Oops, please accept my apologies. I got caught by the Eclipse compiler
> >>> being more forgiving (or more powerful) than the Oracle compiler in the
> >>> generics department. All of that despite the Maven partial builds I
> ran.
> >> I
> >>> must have not run the clean goal or some-such.
> >>>
> >>> Gary
> >>>
> >>>
>  Ralph
> 
> > On Jan 18, 2018, at 9:28 PM, Ralph Goers  >
>  wrote:
> >
> > -1
> >
> > Please revert and move this to the log4j plugins project.
> >
> > Ralph
> >
> >> On Jan 18, 2018, at 8:54 PM, ggreg...@apache.org wrote:
> >>
> >> Repository: logging-log4j2
> >> Updated Branches:
> >> refs/heads/master bb6fcd09e -> 639f093b8
> >>
> >>
> >> [LOG4J2-2186] Add a JDBC ConnectionSource that provides pooling
> >> through
> >> Apache Commons DBCP 2.
> >>
> >> Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
> >> Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/
>  commit/639f093b
> >> Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/
>  639f093b
> >> Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/
>  639f093b
> >>
> >> Branch: refs/heads/master
> >> Commit: 639f093b8103df2c2eda8d62fd12d7619d98ac04
> >> Parents: bb6fcd0
> >> Author: Gary Gregory 
> >> Authored: Thu Jan 18 20:54:47 2018 -0700
> >> Committer: Gary Gregory 
> >> Committed: Thu Jan 18 20:54:47 2018 -0700
> >>
> >> 
> >> --
> >> log4j-jdbc-dbcp2/pom.xml| 170
>  +++
> >> .../db/jdbc/PoolingDriverConnectionSource.java  | 155
> >> +
> >> log4j-jdbc-dbcp2/src/site/manual/index.md   |  35 
> >> log4j-jdbc-dbcp2/src/site/site.xml  |  52 ++
> >> .../jdbc/PoolingDriverConnectionSourceTest.java |  96 +++
> >> pom.xml |   1 +
> >> src/changes/changes.xml |   3 +
> >> src/site/xdoc/manual/appenders.xml  |  28 ++-
> >> 8 files changed, 537 insertions(+), 3 deletions(-)
> >> 
> >> --
> >>
> >>
> >> http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/
>  639f093b/log4j-jdbc-dbcp2/pom.xml
> >> 
> >> --
> >> diff --git a/log4j-jdbc-dbcp2/pom.xml b/log4j-jdbc-dbcp2/pom.xml
> >> new file mode 100644
> >> index 000..18e0e86
> >> --- /dev/null
> >> +++ b/log4j-jdbc-dbcp2/pom.xml
> >> @@ -0,0 +1,170 @@
> >> +
> >> +
> >> +
> >> +http://maven.apache.org/POM/4.0.0; xmlns:xsi="
>  http://www.w3.org/2001/XMLSchema-instance;
> >> +  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>  http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> >> +  
> >> +org.apache.logging.log4j
> >> +log4j
> >> +2.10.1-SNAPSHOT
> >> +  
> >> +  4.0.0
> >> +
> >> +  log4j-jdbc-dbcp2
> >> +  Apache

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

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

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

[log4cxx] Current State

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

5 matches

Site Navigation

Mail list logo

Footer information