The reason for the failure is pretty obvious, I forgot to update the jython
shim. What I'm a bit more confused about is why 'make test' didn't catch
this. I believe I have all the necessary prerequisites to exercise the
jython shim via the JNI tests on my system, however that doesn't appear to
be
Hiram Chirino created PROTON-271:
Summary: proton-hawtdispatch transport not properly encoding PLAIN
sasl user/password.
Key: PROTON-271
URL: https://issues.apache.org/jira/browse/PROTON-271
Project:
[
https://issues.apache.org/jira/browse/PROTON-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated PROTON-271:
-
Attachment: PROTON-271.patch
Attaching patch that fixes the issue.
On Thu, Mar 14, 2013 at 10:50 AM, Ken Giusti kgiu...@redhat.com wrote:
- Original Message -
From: Rafael Schloming r...@alum.mit.edu
To: proton@qpid.apache.org
Sent: Thursday, March 14, 2013 10:07:02 AM
Subject: Re: Why 2 space indentations??
On Thu, Mar 14, 2013 at 9:18
If I see NO-JIRA then I usually infer that the author considered whether a
Jira was required and decided not. Without this marker, I can't
distinguish between deliberate and accidental omission of the Jira number.
On 14 March 2013 14:47, Rafael Schloming r...@alum.mit.edu wrote:
To be
I definitely agree we should make both the longer term roadmap and the
things being actively worked on for the next release more visible.
One frustration I've had with our communication tools has been with the
wiki. I actually had quite a good experience at first. I was happy with how
easy it was
Surely either way you need to read the actual log message to distinguish
between correct and incorrect omission of the JIRA number. I would hate to
think you'd let something like NO-JIRA: overhauled user facing API go by
just because it was prefixed. ;-)
--Rafael
On Thu, Mar 14, 2013 at 11:38
[
https://issues.apache.org/jira/browse/PROTON-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602393#comment-13602393
]
Robbie Gemmell commented on PROTON-270:
---
I dont particularly mind the group id, as I
So..NO-JIRA came about for two reasons.
First, as a way to escape the commit-hook level checking we voted that we
wanted in order to semi-enforce that people had a JIRA in their commit log,
because we were down in the ridiculous ~30% inclusion range not so many
years ago. Infra ultimately said
Alan Conway created PROTON-272:
--
Summary: ctest to run python tests on an installed system.
Key: PROTON-272
URL: https://issues.apache.org/jira/browse/PROTON-272
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-272:
---
Summary: Run tests on an installed system. (was: ctest to run python tests
on an installed system.)
Alan Conway created PROTON-273:
--
Summary: Fix disabled ruby test can have nil content
Key: PROTON-273
URL: https://issues.apache.org/jira/browse/PROTON-273
Project: Qpid Proton
Issue Type:
[
https://issues.apache.org/jira/browse/PROTON-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated PROTON-273:
---
Assignee: Darryl L. Pierce
Fix disabled ruby test can have nil content
[
https://issues.apache.org/jira/browse/PROTON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602575#comment-13602575
]
Alan Conway commented on PROTON-215:
Added ruby tests:
r1456613 | PROTON-215: Added
[
https://issues.apache.org/jira/browse/PROTON-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602578#comment-13602578
]
michael goulish commented on PROTON-260:
Checked in trunk/docs/messenger
On Tue, Mar 5, 2013 at 9:08 AM, Bozo Dragojevic bo...@digiverse.si wrote:
Where in the repository can I see which revision/branch/tag are the
release candidates?
Thanks,
Bozzo
FYI, all the releases are now available at both
https://svn.apache.org/repos/asf/qpid/proton/tags/0.x and
[
https://issues.apache.org/jira/browse/PROTON-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602609#comment-13602609
]
Alan Conway commented on PROTON-215:
It remains to add PHP tests.
[
https://issues.apache.org/jira/browse/PROTON-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-269.
Resolution: Fixed
Fix Version/s: 0.5
Assignee: Rafael H. Schloming
18 matches
Mail list logo