[
https://issues.apache.org/jira/browse/QPID-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797474#action_12797474
]
Rajith Attapattu commented on QPID-2283:
The first attempt at resolving the above is
I think I agree with all you said there - except it doesn't explain why
we've got 3 branches for 0.5 -
0.5-release
0.5.x-dev
0.5-fix
And of course I can't tell fro svn what relationship (if any) these
branches have to each other.
Andrew
On Wed, 2010-01-06 at 22:28 +, Robbie Gemmell wrote:
On Wed, 2010-01-06 at 17:25 -0500, Andrew Stitcher wrote:
> On Wed, 2010-01-06 at 22:14 +, Robbie Gemmell wrote:
> > I only ask as both already exist.
>
> Bugger, you're right - I'm starting to hate svn branching.
>
> I'll fix it (when I figure out the idiot thing I did)
Figured it out and f
Oh, and I forgot to add that I think Tag names should just be the direct
version number, e.g. simply M4, 0.5, 0.6, 0.6.1 etc
Robbie
> -Original Message-
> From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
> Sent: 06 January 2010 22:22
> To: dev@qpid.apache.org
> Subject: RE: Tagging
On Wed, 2010-01-06 at 22:14 +, Robbie Gemmell wrote:
> I only ask as both already exist.
Bugger, you're right - I'm starting to hate svn branching.
I'll fix it (when I figure out the idiot thing I did)
Andrew
-
Apache Qpi
As far as I understand, the rationale for creating the 0.X-release branch is
just so that trunk can be unfrozen and any blockers committed back to the
branch. When releases drag on like M4 and 0.5 did it is quite annoying having
trunk frozen.
We could as easily use the same temporary branch nam
I only ask as both already exist.
Robbie
> -Original Message-
> From: Andrew Stitcher [mailto:astitc...@redhat.com]
> Sent: 06 January 2010 22:09
> To: dev@qpid.apache.org
> Subject: RE: Subversion tags and branches (a little moan)
>
> On Wed, 2010-01-06 at 22:00 +, Robbie Gemmell wr
On Wed, 2010-01-06 at 21:51 +, Robbie Gemmell wrote:
> Shall we retroactively create a 0.5 tag for future usage? Andrews suggestion
> of looking at the .svnrevision file doesn't work for 0.5 as it reports HEAD.
Oh - I think retroactively creating the tag would be useful.
Thinking a little ab
On Wed, 2010-01-06 at 22:00 +, Robbie Gemmell wrote:
> It is indeed unfortunate, and I try my best to remember it when dealing with
> branches.
>
> While the topic is raised though, is the 0.6 branch rooted at:
> https://svn.apache.org/repos/asf/qpid/branches/0.6-release/qpid or
This one (ab
I see this has been marked resolved for 0.7, was it decided it isn't a blocker?
Robbie
> -Original Message-
> From: Carl Trieloff [mailto:cctriel...@redhat.com]
> Sent: 04 January 2010 21:23
> To: dev@qpid.apache.org
> Subject: Re: [jira] Created: (QPID-2320) Failed acquire on LVQ causes
It is indeed unfortunate, and I try my best to remember it when dealing with
branches.
While the topic is raised though, is the 0.6 branch rooted at:
https://svn.apache.org/repos/asf/qpid/branches/0.6-release/qpid or
https://svn.apache.org/repos/asf/qpid/branches/0.6-release/trunk/qpid ?
Robbie
Robert Godfrey wrote:
I don't wish to overcomplicate, but do you want some grouping of features...
(e.g. a parentFeature tag) if we're looking at the same sort of granularity
as unit tests, that should be quite fine... but many of them may be aspects
of the same "feature"...
Quite possibly. I
Shall we retroactively create a 0.5 tag for future usage? Andrews suggestion of
looking at the .svnrevision file doesn't work for 0.5 as it reports HEAD.
I just noticed from the users list why Rajith wanted to know the revision, and
he understandably got the wrong revision from looking at the 0.
[
https://issues.apache.org/jira/browse/QPID-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Trieloff resolved QPID-2320.
-
Resolution: Fixed
Fix Version/s: 0.7
Committed revision 896687.
test and fix
> Failed ac
I've just noticed (after several hours of puzzling about what was
screwing up my git branch history) that there are a number of branches
and tags that omit the top level, redundant "qpid" directory.
Now I'm for getting rid of uselessness like this as much as the next guy
(and I'm in fact responsib
On Wed, 2010-01-06 at 15:29 -0500, Rajith Attapattu wrote:
> I was just trying to quickly figure out the svn rev the Java 0.5
> release and found that there wasn't a tag available for it.
> (please note we do have a branch for it, but I still think we should
> be tagging the final release).
> It se
[
https://issues.apache.org/jira/browse/QPID-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797303#action_12797303
]
Ian Main commented on QPID-1880:
Actually we had a conversation on irc and figured that so l
[
https://issues.apache.org/jira/browse/QPID-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2334:
--
Assignee: Ted Ross
> Strange hang in console
> ---
>
> Key: QPID-233
[
https://issues.apache.org/jira/browse/QPID-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2333:
--
Assignee: Ted Ross
> Seemingly random timeouts
> -
>
> Key: QPID
I was just trying to quickly figure out the svn rev the Java 0.5
release and found that there wasn't a tag available for it.
(please note we do have a branch for it, but I still think we should
be tagging the final release).
It seems we have tags for the previous releases (all though some
aren't ex
I don't wish to overcomplicate, but do you want some grouping of features...
(e.g. a parentFeature tag) if we're looking at the same sort of granularity
as unit tests, that should be quite fine... but many of them may be aspects
of the same "feature"...
-- Rob
2010/1/6 Rafael Schloming
> Alan
[
https://issues.apache.org/jira/browse/QPID-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797298#action_12797298
]
Ian Main commented on QPID-2334:
Actually this seems to be the most common error I'm seeing
Strange hang in console
---
Key: QPID-2334
URL: https://issues.apache.org/jira/browse/QPID-2334
Project: Qpid
Issue Type: Bug
Components: Qpid Managment Framework
Environment: qmf-0.5.829175-3.fc11.x86_
[
https://issues.apache.org/jira/browse/QPID-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797294#action_12797294
]
Rajith Attapattu commented on QPID-1875:
Martin I cannot recall who added the option
[
https://issues.apache.org/jira/browse/QPID-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797286#action_12797286
]
Ian Main commented on QPID-2330:
I actually think this may be a thread deadlock and may be t
[
https://issues.apache.org/jira/browse/QPID-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797285#action_12797285
]
Ian Main commented on QPID-2333:
We saw this happen in ovirt a lot as well. Which is kind o
Alan Conway wrote:
On 01/06/2010 06:52 AM, Robert Godfrey wrote:
2010/1/6 Rafael Schloming
Robert Godfrey wrote:
Overall I think with a bit of work from both the C++ and Java
communities
we
can get the brokers to look and behave much more similarly...
however we
will also need to change th
Seemingly random timeouts
-
Key: QPID-2333
URL: https://issues.apache.org/jira/browse/QPID-2333
Project: Qpid
Issue Type: Bug
Environment: qmf-0.5.829175-3.fc11.x86_64
Running console and qpidd on one machin
[
https://issues.apache.org/jira/browse/QPID-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2332:
--
Assignee: Ted Ross
> Would be nice to have some kind of wait_for() functionality in the console API
> --
[
https://issues.apache.org/jira/browse/QPID-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2331:
--
Assignee: Ted Ross
> C++ based ruby console leaks memory?
>
>
>
Would be nice to have some kind of wait_for() functionality in the console API
--
Key: QPID-2332
URL: https://issues.apache.org/jira/browse/QPID-2332
Project: Qpid
I
C++ based ruby console leaks memory?
Key: QPID-2331
URL: https://issues.apache.org/jira/browse/QPID-2331
Project: Qpid
Issue Type: Bug
Components: Qpid Managment Framework
Environment:
[
https://issues.apache.org/jira/browse/QPID-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2328:
--
Assignee: Ted Ross
> Querying for 500 objects causes C++ based ruby console to hang
> --
[
https://issues.apache.org/jira/browse/QPID-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2330:
--
Assignee: Ted Ross
> Querying 30 to 100 objects and then calling methods causes some methods to
> not r
[
https://issues.apache.org/jira/browse/QPID-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2329:
--
Assignee: Ted Ross
> Queries require lower case versions of class names?
> -
Querying 30 to 100 objects and then calling methods causes some methods to not
return?
--
Key: QPID-2330
URL: https://issues.apache.org/jira/browse/QPID-2330
Project:
Queries require lower case versions of class names?
---
Key: QPID-2329
URL: https://issues.apache.org/jira/browse/QPID-2329
Project: Qpid
Issue Type: Bug
Components: Qpid Managment Fr
Querying for 500 objects causes C++ based ruby console to hang
--
Key: QPID-2328
URL: https://issues.apache.org/jira/browse/QPID-2328
Project: Qpid
Issue Type: Bug
Compone
> On 01/06/2010 11:20 AM, john dunning wrote:
> > On Wed, 2010-01-06 at 16:11 +, Gordon Sim wrote:
> >> On 01/06/2010 04:05 PM, Alan Conway wrote:
> >
> >>> Thats true, but I think it is still worth splitting out test sets
> >>> for optional modules into separate files for the sake of
> clari
On Tue, Jan 5, 2010 at 7:42 PM, Rajith Attapattu wrote:
> It appears that there are two different means configuring the
> heartbeat interval for the JMS client.
> The 0-9 codepath uses a jvm argument while the 0-10 codepath uses a
> broker URL property.
>
> From a users perspective we should prov
[
https://issues.apache.org/jira/browse/QPID-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-2327:
--
Assignee: Ted Ross
> Enhance qpid-config to deal with xml and headers brokers
>
[
https://issues.apache.org/jira/browse/QPID-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
john dunning updated QPID-2327:
---
Attachment: bz-549443.patch
This patch implements the new qpid-config functionality, and enhances the
Enhance qpid-config to deal with xml and headers brokers
Key: QPID-2327
URL: https://issues.apache.org/jira/browse/QPID-2327
Project: Qpid
Issue Type: Improvement
Components:
On 01/06/2010 11:20 AM, john dunning wrote:
On Wed, 2010-01-06 at 16:11 +, Gordon Sim wrote:
On 01/06/2010 04:05 PM, Alan Conway wrote:
Thats true, but I think it is still worth splitting out test sets for
optional modules into separate files for the sake of clarity and
readability.
Yes
On Wed, 2010-01-06 at 16:11 +, Gordon Sim wrote:
> On 01/06/2010 04:05 PM, Alan Conway wrote:
> > Thats true, but I think it is still worth splitting out test sets for
> > optional modules into separate files for the sake of clarity and
> > readability.
>
> Yes, thats a fair point.
Thanks al
On 01/06/2010 04:05 PM, Alan Conway wrote:
On 01/06/2010 06:14 AM, Gordon Sim wrote:
On 01/04/2010 06:41 PM, john dunning wrote:
I'm squiffing up qpid-config to add the ability to configure xml
exchanges and queue bindings. I'm trying to add stuff to the test suite
(cpp/src/tests/cli_tests.py a
On 01/06/2010 06:52 AM, Robert Godfrey wrote:
2010/1/6 Rafael Schloming
Robert Godfrey wrote:
Overall I think with a bit of work from both the C++ and Java communities
we
can get the brokers to look and behave much more similarly... however we
will also need to change the way we work a bit so
On 01/06/2010 06:14 AM, Gordon Sim wrote:
On 01/04/2010 06:41 PM, john dunning wrote:
I'm squiffing up qpid-config to add the ability to configure xml
exchanges and queue bindings. I'm trying to add stuff to the test suite
(cpp/src/tests/cli_tests.py and related) to match.
The difficulty I have
[
https://issues.apache.org/jira/browse/QPID-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797149#action_12797149
]
Alan Conway commented on QPID-1982:
---
We already have portable constructs for this type of
exchange.declare should throw a 404 - not found exception if the exchange type
is unknown
-
Key: QPID-2326
URL: https://issues.apache.org/jira/browse/QPID-2326
Pr
On Fri, 2009-12-18 at 12:48 -0500, Rafael Schloming wrote:
> Rafael Schloming wrote:
> > As there have been no comments or questions on the discussion thread,
> > I'm going to move this to a vote:
> >
> > Qualities we look for:
> >
> > - A candidate must demonstrate an understanding of how our
On Wed, Jan 06, 2010 at 09:19:57AM -0500, Ted Ross wrote:
> The problem is that you've built without the cyrus-sasl-devel. The
> client in that test tries to set the user-id header with information
> extracted from the sasl context (which isn't there). This test should
> be disabled in the --w
On 01/06/2010 08:46 AM, Ján Sáreník wrote:
Hello!
On current trunk (r896256) I am getting this error
after compiling --with-swig (see attachment) and
running 'make check'.
Best regards, Jan Sarenik
-
Apache Qpid
Hello!
On current trunk (r896256) I am getting this error
after compiling --with-swig (see attachment) and
running 'make check'.
Best regards, Jan Sarenik
make[3]: Entering directory `/home/jsarenik/qpid/qpid/cpp/bindings/qmf/tests'
Running qmf interop tests using broker on port 40430
P
[Java Broker] SASL PLAIN authentication does not work when both an
authentication and authorization id are supplied
---
Key: QPID-2325
URL: https://iss
message_cancel should throw 404 not-found exception if subscription does not
exist
--
Key: QPID-2324
URL: https://issues.apache.org/jira/browse/QPID-2324
Project: Qpid
2010/1/6 Rafael Schloming
> Robert Godfrey wrote:
>
>> Overall I think with a bit of work from both the C++ and Java communities
>> we
>> can get the brokers to look and behave much more similarly... however we
>> will also need to change the way we work a bit so that when we decide to
>> add
>>
[
https://issues.apache.org/jira/browse/QPID-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797080#action_12797080
]
Gordon Sim commented on QPID-2104:
--
The property used as the key should ideally be configur
Robert Godfrey wrote:
Overall I think with a bit of work from both the C++ and Java communities we
can get the brokers to look and behave much more similarly... however we
will also need to change the way we work a bit so that when we decide to add
new features we attempt to discuss and agree bef
On 01/04/2010 06:41 PM, john dunning wrote:
I'm squiffing up qpid-config to add the ability to configure xml
exchanges and queue bindings. I'm trying to add stuff to the test suite
(cpp/src/tests/cli_tests.py and related) to match.
The difficulty I have right now is that the xml support is opti
On 01/04/2010 04:27 PM, Robert Godfrey wrote:
Happy New Year all...
So, at the start of this new year I think it is important that we try to
focus on improving the experience of our project... and in particular I
think we should be looking at making the project look like a single coherent
whole.
On 01/05/2010 06:54 PM, Steve Huston wrote:
Hi Kerry,
Thought I'd mention this - I get some errors building a clean
trunk on Ubuntu and Windows.
On Windows, I'm running VC9 SP1 on XP (fully patched), CMake
2.8.0, boost 1.3.9 against r896143, clean checkout.
cpp\src\qmf\engine\ResilientConne
62 matches
Mail list logo
