Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-04 Thread Rob Godfrey
+1 built from source, ran 0-9-1 and 1-0 tests, started up the broker and kicked the tires. Tested the new REST API parts on various JVMs (8, 11 ; hotspot, J9) on my OS X machine. -- Rob On Mon, 2 Dec 2019 at 11:28, Alex Rudyy wrote: > Hi all, > > I built release artefacts for Qpid Broker-J ver

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Gordon Sim
On 03/12/2019 5:59 pm, Oleksandr Rudyy wrote: Gordon, You can use use one of maven surefire plugin exclude mechanisms. The simplest way is to build with an option '-Dtest=!SpnegoAuthenticatorTest,!KerberosAuthenticationManagerTest' Thanks! Skipping those and also org.apache.qpid.server.loggin

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Robbie Gemmell
Alex has replied showing how to can just exclude those specific tests. More generally though, what you see is just standard maven behaviour for a multi-module builds where if a module (via tests in this case) build fails then the overall build stops after that unless instructed otherwise, presumab

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Oleksandr Rudyy
Gordon, You can use use one of maven surefire plugin exclude mechanisms. The simplest way is to build with an option '-Dtest=!SpnegoAuthenticatorTest,!KerberosAuthenticationManagerTest' Alternatively, you can specify exclude file using option -Dsurefire.excludesFile=/path/to/exclude/file. For exa

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Gordon Sim
On 03/12/2019 5:07 pm, Oleksandr Rudyy wrote: Hi Gordon. The tests from test suites KerberosAuthenticationManagerTest and SpnegoAuthenticatorTest are failing sporadically in Apache Jenkins builds. I have not seen them failing locally on my machine. I suspect that it is an issue with embedded Ap

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Oleksandr Rudyy
Hi Gordon. The tests from test suites KerberosAuthenticationManagerTest and SpnegoAuthenticatorTest are failing sporadically in Apache Jenkins builds. I have not seen them failing locally on my machine. I suspect that it is an issue with embedded Apache Kerby implementation of Kerberos server. I

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Gordon Sim
On 02/12/2019 10:28 am, Alex Rudyy wrote: Hi all, I built release artefacts for Qpid Broker-J version 7.1.6 RC1. Please, give them a test out and vote accordingly. The source and binary archives can be found at: https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.1.6-rc1/ The maven artifact

RE: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread VERMEULEN Olivier
-Original Message- From: Robbie Gemmell Sent: mardi 3 décembre 2019 13:49 To: users@qpid.apache.org Subject: Re: [VOTE] Release Qpid Broker-J 7.1.6 +1 I checked things over as below: - Verified the signature and checksum files. - Used mvn apache-rat:check to verify the headers in the source archive

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-03 Thread Robbie Gemmell
+1 I checked things over as below: - Verified the signature and checksum files. - Used mvn apache-rat:check to verify the headers in the source archive. - Checked for LICENCE + NOTICE files present in the archives. - Started brokers from the binary archive, created queues using the console, on JDK

Re: [VOTE] Release Qpid Broker-J 7.1.6

2019-12-02 Thread Oleksandr Rudyy
+1 My testing included the following: * verified signatures and checksums * built and ran tests successfully from source bundle using openjdk version "1.8.0_232" * verified that new statistics (processCpuLoad and processCpuTime) are reported via REST API * verified that consumerId is reported by q