Re: [Log4j] Jenkins pipeline mostly set up

2018-04-10 Thread Ralph Goers
I don’t know. I have never really looked at how Jenkins does the deploy. Ralph > On Apr 10, 2018, at 7:16 PM, Matt Sicker wrote: > > Is it possible to exclude that from the deploy task? The scala api build > only publishes the api jars, not the samples, for example. > > On 10 April 2018 at 17

Re: [Log4j] Jenkins pipeline mostly set up

2018-04-10 Thread Matt Sicker
Is it possible to exclude that from the deploy task? The scala api build only publishes the api jars, not the samples, for example. On 10 April 2018 at 17:12, Ralph Goers wrote: > Note that the Jenkins deployment uploads stuff that we don’t release. > > Ralph > > > On Apr 10, 2018, at 9:57 AM, M

Re: [log4j]

2018-04-10 Thread Remko Popma
I saw some commits flying by in that area recently but I didn’t look closely. Could that be related? Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Apr 11, 2018, at 4:50, Gary Gregory wrote: > > When I change my log4j XML config file and I have status loggi

Re: [Log4j] Jenkins pipeline mostly set up

2018-04-10 Thread Ralph Goers
Note that the Jenkins deployment uploads stuff that we don’t release. Ralph > On Apr 10, 2018, at 9:57 AM, Matt Sicker wrote: > > I've added a new pipeline for Log4j < > https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are > doing in log4net, chainsaw, log4j scala api, log4j

Re: [log4j] com.lmax.disruptor.collections.Histogram gone in LMAX 3.4.x

2018-04-10 Thread Gary Gregory
Until someone wants to do that ;-) I copied the LMAX class into our test code base. Gary On Sun, Apr 8, 2018 at 4:30 PM, Remko Popma wrote: > We should probably migrate to HdrHistogram, but I don’t have time to do > that work now. > > (Shameless plug) Every java main() method deserves http://pi

[log4j]

2018-04-10 Thread Gary Gregory
When I change my log4j XML config file and I have status logging set to DEBUG, I see: 2018-04-10 13:48:43,895 Log4j2-TF-1-ConfiguratonFileWatcher-3 ERROR Could not register mbeans javax.management.InstanceAlreadyExistsException: org.apache.logging.log4j2:type=6d06d69c at com.sun.jmx.mbeanserver.Re

[Log4j] Jenkins pipeline mostly set up

2018-04-10 Thread Matt Sicker
I've added a new pipeline for Log4j < https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and logging parent. Thanks to Dominik for demonstrating that this was possible and also how to run things on Windows. This pi

Re: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-10 Thread Matt Sicker
Strange, I thought this file was generated by the maven doap plugin. On 10 April 2018 at 04:27, sebb wrote: > As the subject says: the asfext:pmc value is incorrect; it must point > to a PMC not a release. > > > -- Forwarded message -- > From: Projects > Date: 10 April 2018 at 0

Fwd: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap_log4j.rdf

2018-04-10 Thread sebb
As the subject says: the asfext:pmc value is incorrect; it must point to a PMC not a release. -- Forwarded message -- From: Projects Date: 10 April 2018 at 03:00 Subject: WARN: invalid asfext:pmc 'https://logging.apache.org/log4j/2.x/' in https://logging.apache.org/log4j/2.x/doap