[GitHub] qpid-dispatch pull request #179: Update qdmanage, qdrouterd, and qdstat man ...

2017-07-18 Thread bhardesty
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/179 Update qdmanage, qdrouterd, and qdstat man pages * Fixed typos * Edited for consistency * Edited and rephrased some field descriptions for clarity You can merge this pull request

[jira] [Commented] (QPID-7865) [Java Broker] Tidy-up AMQP 1.0 'Destination' classes

2017-07-18 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092097#comment-16092097 ] ASF subversion and git services commented on QPID-7865: --- Commit

[jira] [Created] (QPID-7865) [Java Broker] Tidy-up AMQP 1.0 'Destination' classes

2017-07-18 Thread Rob Godfrey (JIRA)
Rob Godfrey created QPID-7865: - Summary: [Java Broker] Tidy-up AMQP 1.0 'Destination' classes Key: QPID-7865 URL: https://issues.apache.org/jira/browse/QPID-7865 Project: Qpid Issue Type:

[jira] [Commented] (QPID-7864) [Java Broker] Update Google Guava dependency

2017-07-18 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092061#comment-16092061 ] ASF subversion and git services commented on QPID-7864: --- Commit

[jira] [Created] (QPID-7864) [Java Broker] Update Google Guava dependency

2017-07-18 Thread Keith Wall (JIRA)
Keith Wall created QPID-7864: Summary: [Java Broker] Update Google Guava dependency Key: QPID-7864 URL: https://issues.apache.org/jira/browse/QPID-7864 Project: Qpid Issue Type: Improvement

[jira] [Commented] (QPID-7789) [Java Broker, WMC] The webclient sasl implementation should always answer a challenge by sending back a response.

2017-07-18 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091784#comment-16091784 ] ASF subversion and git services commented on QPID-7789: --- Commit

[jira] [Commented] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091752#comment-16091752 ] Jason Frey commented on PROTON-1519: I don't know how to add Ruby versions to the test matrix. I see

[jira] [Commented] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091746#comment-16091746 ] Jason Frey commented on PROTON-1519: Made a PR to fix: https://github.com/apache/qpid-proton/pull/111

[GitHub] qpid-proton pull request #111: Fix mapping of LONG for Ruby 2.4+

2017-07-18 Thread Fryguy
GitHub user Fryguy opened a pull request: https://github.com/apache/qpid-proton/pull/111 Fix mapping of LONG for Ruby 2.4+ (Ruby 2.4.1) > irb > RUBY_VERSION < "2.4" ? [Fixnum, Bignum] : [Integer] => [Integer] (Ruby 2.3.3) > irb > RUBY_VERSION < "2.4" ? [Fixnum,

[jira] [Comment Edited] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091731#comment-16091731 ] Jason Frey edited comment on PROTON-1519 at 7/18/17 3:43 PM: - I think I see

[jira] [Commented] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091731#comment-16091731 ] Jason Frey commented on PROTON-1519: I think I see the issue. In Ruby 2.4, Fixnum and Bignum classes

[jira] [Created] (QPID-7863) qpidd-1.36 init script fails with "source: not found" on ubuntu

2017-07-18 Thread Chris Richardson (JIRA)
Chris Richardson created QPID-7863: -- Summary: qpidd-1.36 init script fails with "source: not found" on ubuntu Key: QPID-7863 URL: https://issues.apache.org/jira/browse/QPID-7863 Project: Qpid

[jira] [Comment Edited] (QPID-7815) Reject policy type

2017-07-18 Thread Tomas Soltys (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091640#comment-16091640 ] Tomas Soltys edited comment on QPID-7815 at 7/18/17 2:44 PM: - Hi, there is

[jira] [Comment Edited] (QPID-7815) Reject policy type

2017-07-18 Thread Tomas Soltys (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091640#comment-16091640 ] Tomas Soltys edited comment on QPID-7815 at 7/18/17 2:43 PM: - Hi, there is

[jira] [Updated] (QPID-7815) Reject policy type

2017-07-18 Thread Tomas Soltys (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Soltys updated QPID-7815: --- Attachment: 1 before restart.png 2 after restart.png broker.log

[jira] [Updated] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Frey updated PROTON-1519: --- Description: qpid_proton 0.17.0 was built successfully from source with {code} > cmake

[jira] [Created] (PROTON-1519) qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1

2017-07-18 Thread Jason Frey (JIRA)
Jason Frey created PROTON-1519: -- Summary: qpid_proton 0.17.0 Ruby gem does not work with Ruby 2.4.1 Key: PROTON-1519 URL: https://issues.apache.org/jira/browse/PROTON-1519 Project: Qpid Proton

[jira] [Commented] (QPIDJMS-294) The SCRAM-SHA-* SASL mechanisms should verify the server final message if it is sent in the additional-data field of sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091515#comment-16091515 ] Keith Wall commented on QPIDJMS-294: Great. I did test the changes with the Java Broker, all was

[jira] [Commented] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091485#comment-16091485 ] Keith Wall commented on PROTON-1486: Raised JIRA to track Proton-C equivalent change PROTON-1518. >

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Issue Type: Improvement (was: Bug) > Proton provides no mechanism to get or set the additional-data

[jira] [Commented] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091482#comment-16091482 ] Keith Wall commented on PROTON-1518: Alex and I looked into Proton-C's source whilst doing the

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Description: This JIRA refers to Proton(-C) only.Analogous work was already carried out for

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Description: This JIRA refers to Proton(-C) only.Analogous work was already carried out for

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Affects Version/s: (was: proton-j-0.19.0) > Proton provides no mechanism to get or set the

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Fix Version/s: (was: proton-j-0.20.0) > Proton provides no mechanism to get or set the

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Component/s: (was: proton-j) proton-c > Proton provides no mechanism to get or

[jira] [Created] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
Keith Wall created PROTON-1518: -- Summary: Proton provides no mechanism to get or set the additional-data field on sasl-outcome Key: PROTON-1518 URL: https://issues.apache.org/jira/browse/PROTON-1518

[jira] [Updated] (PROTON-1518) Proton provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Keith Wall (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1518: --- Description: This JIRA refers to The Proton Engine API provides no mechanism for getting or setting

[jira] [Updated] (QPIDJMS-294) The SCRAM-SHA-* SASL mechanisms should verify the server final message if it is sent in the additional-data field of sasl-outcome

2017-07-18 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-294: --- Affects Version/s: 0.23.0 > The SCRAM-SHA-* SASL mechanisms should verify the server final

[jira] [Commented] (QPIDJMS-294) The SCRAM-SHA-* SASL mechanisms should verify the server final message if it is sent in the additional-data field of sasl-outcome

2017-07-18 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091460#comment-16091460 ] ASF GitHub Bot commented on QPIDJMS-294: Github user gemmellr commented on the issue:

[jira] [Updated] (QPIDJMS-294) The SCRAM-SHA-* SASL mechanisms should verify the server final message if it is sent in the additional-data field of sasl-outcome

2017-07-18 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPIDJMS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-294: --- Fix Version/s: 0.24.0 > The SCRAM-SHA-* SASL mechanisms should verify the server final

[GitHub] qpid-jms issue #9: QPIDJMS-294: Ensure that SASL mechanism has completed bef...

2017-07-18 Thread gemmellr
Github user gemmellr commented on the issue: https://github.com/apache/qpid-jms/pull/9 Looks good. I gave things a try with the changes from PROTON-1486 (now pushed) against Dispatch and the C++ broker, which continue to send the explicit challange before the outcome rather than use

[jira] [Commented] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091447#comment-16091447 ] Robbie Gemmell commented on PROTON-1486: [~k-wall]: PR looks good, merged. [~alex.rufous]: can

[jira] [Resolved] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1486. Resolution: Fixed Fix Version/s: proton-j-0.20.0 > Proton(-J) provides no mechanism

[jira] [Updated] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1486: --- Affects Version/s: proton-j-0.19.0 > Proton(-J) provides no mechanism to get or set the

[jira] [Commented] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091446#comment-16091446 ] ASF GitHub Bot commented on PROTON-1486: Github user asfgit closed the pull request at:

[jira] [Commented] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091444#comment-16091444 ] ASF subversion and git services commented on PROTON-1486: - Commit

[jira] [Commented] (PROTON-1486) Proton(-J) provides no mechanism to get or set the additional-data field on sasl-outcome

2017-07-18 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16091445#comment-16091445 ] ASF subversion and git services commented on PROTON-1486: - Commit

[GitHub] qpid-proton-j pull request #9: PROTON-1486: Expose SaslOutcome additional-da...

2017-07-18 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton-j/pull/9 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Resolved] (QPID-7815) Reject policy type

2017-07-18 Thread Alex Rudyy (JIRA)
[ https://issues.apache.org/jira/browse/QPID-7815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7815. -- Resolution: Fixed Resolving the JIRA as required changes are implemented. Keith and I worked in pair at