[
https://issues.apache.org/jira/browse/QPID-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-5614:
--
Component/s: Java Broker
> Fix Java Broker QMF2 Plugin problems caused by refactoring in QPID-5
mmit 1763292 from [~godfrer] in branch 'qpid/trunk'
[ https://svn.apache.org/r1763292 ]
QPID-7446 : Allow the QMF2 plugin to compile against the 6.0.x java codebase
> Allow Java QMF2 plugin to compile against
Rob Godfrey created QPID-7446:
-
Summary: Allow Java QMF2 plugin to compile against the 6.0.x broker
Key: QPID-7446
URL: https://issues.apache.org/jira/browse/QPID-7446
Project: Qpid
Issue Type
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-5820.
--
Resolution: Fixed
> Update QMF2 plugin wrt changes made to Broker mode during 0
[
https://issues.apache.org/jira/browse/QPID-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6059.
--
> Java QMF2 Agent code made some now invalid assumptions about repl
[
https://issues.apache.org/jira/browse/QPID-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-6059.
Resolution: Fixed
> Java QMF2 Agent code made some now invalid assumptions about repl
mmit 1621430 from [~fadams] in branch 'qpid/trunk'
[ https://svn.apache.org/r1621430 ]
QPID-6059: Java QMF2 Agent code made some now invalid assumptions about replyTo
> Java QMF2 Agent code made some now invalid assumpti
Fraser Adams created QPID-6059:
--
Summary: Java QMF2 Agent code made some now invalid assumptions
about replyTo
Key: QPID-6059
URL: https://issues.apache.org/jira/browse/QPID-6059
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated QPID-6024:
--
Fix Version/s: (was: 0.31)
0.30
> Changes to Java Broker Model affected Q
mmit 1620361 from [~godfrer] in branch 'qpid/branches/0.30'
[ https://svn.apache.org/r1620361 ]
Merge r1619137 from trunk to address QPID-6024
> Changes to Java Broker Model affected QMF2 plugin
> -
>
> Key: QPID-
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-6024:
-
Summary: Changes to Java Broker Model affected QMF2 plugin (was: Changes
tp Java Broker Model
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reassigned QPID-6024:
Assignee: Fraser Adams
> Changes tp Java Broker Model affected QMF2 plu
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-6024:
-
Fix Version/s: 0.31
> Changes tp Java Broker Model affected QMF2 plu
cker otherwise hehe)
> Changes tp Java Broker Model affected QMF2 plugin
> -
>
> Key: QPID-6024
> URL: https://issues.apache.org/jira/browse/QPID-6024
> Project: Qpid
> Issue Type:
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-6024.
--
> Changes tp Java Broker Model affected QMF2 plu
[
https://issues.apache.org/jira/browse/QPID-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-6024.
Resolution: Fixed
> Changes tp Java Broker Model affected QMF2 plu
mmit 1619137 from [~fadams] in branch 'qpid/trunk'
[ https://svn.apache.org/r1619137 ]
QPID-6024: Update agentdata/Broker.java to reflect change in Java Broker Model
Port class that changed getAvailableProtocols to getProtocols
> Changes tp Java Broker Model aff
Fraser Adams created QPID-6024:
--
Summary: Changes tp Java Broker Model affected QMF2 plugin
Key: QPID-6024
URL: https://issues.apache.org/jira/browse/QPID-6024
Project: Qpid
Issue Type: Bug
Alan Conway created QPID-6015:
-
Summary: python QMF2 console raises exception due to HA
subscriptions.
Key: QPID-6015
URL: https://issues.apache.org/jira/browse/QPID-6015
Project: Qpid
Issue
nding, but the addBinding method is
the one that results in the QMF Binding instance being created. In other words
the QMF Binding instance was getting constructed before the
resolveAutomatedAttribute stuff
> Update QMF2 plugin wrt changes made to Broker
t being set on
construction which caused getArguments to always return null
> Update QMF2 plugin wrt changes made to Broker mode during 0.29
> --
>
> Key: QPID-5820
> URL: https://issues.apa
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048737#comment-14048737
]
Keith Wall commented on QPID-5820:
--
Fraser,
Andrew and I made changes to get the
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-5820:
-
Status: Reviewable (was: In Progress)
> Update QMF2 plugin wrt changes made to Broker mode during 0
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall reassigned QPID-5820:
Assignee: Keith Wall
> Update QMF2 plugin wrt changes made to Broker mode during 0
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-5820:
-
Assignee: Fraser Adams (was: Keith Wall)
> Update QMF2 plugin wrt changes made to Broker mode dur
mmit 1607034 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1607034 ]
QPID-5820: [Java QMF2 Plugin] changes to plugin owing to the Java Broker model
updates made during 0.29
* Used model getters rather than named attributes wherever possible
Work done by Andrew MacBean and
mmit 1606812 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1606812 ]
QPID-5820: [Java QMF2 Plugin] changes to plugin owing to the Java Broker model
updates made during 0.29
* VHNs (virtualhostnodes) may exist within a VH (virtualhost)
* Use Port#availableProtocols ra
[
https://issues.apache.org/jira/browse/QPID-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-5820:
-
Component/s: Qpid Managment Framework
> Update QMF2 plugin wrt changes made to Broker mode during 0
Keith Wall created QPID-5820:
Summary: Update QMF2 plugin wrt changes made to Broker mode during
0.29
Key: QPID-5820
URL: https://issues.apache.org/jira/browse/QPID-5820
Project: Qpid
Issue
JAkub Scholz created QPID-5728:
--
Summary: qpid-tool shows all objects twice when both QMF1 and QMF2
are enabled
Key: QPID-5728
URL: https://issues.apache.org/jira/browse/QPID-5728
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams resolved QPID-5614.
Resolution: Fixed
> Fix Java Broker QMF2 Plugin problems caused by refactoring in QPID-5
[
https://issues.apache.org/jira/browse/QPID-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924847#comment-13924847
]
Rob Godfrey commented on QPID-5614:
---
bq. The QMF2 Plugin compiles again and mostly w
mmit 1575533 from [~fadams] in branch 'qpid/trunk'
[ https://svn.apache.org/r1575533 ]
QPID-5614: Fix problems caused by changes to Java Broker Logging in QPID-5611
> Fix Java Broker QMF2 Plugin problems caused by refacto
mmit 1575530 from [~fadams] in branch 'qpid/trunk'
[ https://svn.apache.org/r1575530 ]
QPID-5614: Initial fix of the issues. The QMF2 Plugin compiles again and mostly
works, but there are issues with the bindings and subscriptions - though I
think that this might be a problem with t
Fraser Adams created QPID-5614:
--
Summary: Fix Java Broker QMF2 Plugin problems caused by
refactoring in QPID-5578
Key: QPID-5614
URL: https://issues.apache.org/jira/browse/QPID-5614
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams closed QPID-5470.
--
> Improve QMF README documentation and update JavaDocs to reflect new location
> of QMF2 AP
ion
> of QMF2 API docs
> -
>
> Key: QPID-5470
> URL: https://issues.apache.org/jira/browse/QPID-5470
> Project: Qpid
>
mmit 1557407 from [~fadams] in branch 'qpid/trunk'
[ https://svn.apache.org/r1557407 ]
QPID-5470: Improve QMF README documentation and update JavaDocs to reflect new
location of QMF2 API docs
> Improve QMF README documentation and update JavaDocs to reflect new location
&
Fraser Adams created QPID-5470:
--
Summary: Improve QMF README documentation and update JavaDocs to
reflect new location of QMF2 API docs
Key: QPID-5470
URL: https://issues.apache.org/jira/browse/QPID-5470
On Wed, 2013-12-04 at 17:26 -0500, Alan Conway wrote:
> I'm seeing these errors when trying to build the trunk:
>
> In file included from
> /home/aconway/qpid/debug/bindings/qmf2/ruby/rubyRUBY_wrap.cxx:1883:0:
> /home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:26:4: error
Chuck's correct - for some reason the ruby swig is not picking up the following
change to cpp/include/qmf/qmf2.i:
https://svn.apache.org/viewvc/qpid/branches/0.26/qpid/cpp/include/qmf/qmf2.i?r1=1545842&r2=1545841&pathrev=1545842
Andrew and I have hit this before, spent some t
t; To: "Qpid Dev"
> Sent: Wednesday, December 4, 2013 5:26:43 PM
> Subject: qmf2 won't build on trunk
>
> I'm seeing these errors when trying to build the trunk:
>
> In file included from
> /home/aconway/qpid/debug/bindings/qmf2/ruby/rubyRUBY_wrap.cxx:1883:0:
I'm seeing these errors when trying to build the trunk:
In file included from
/home/aconway/qpid/debug/bindings/qmf2/ruby/rubyRUBY_wrap.cxx:1883:0:
/home/aconway/qpid/qpid/cpp/include/qmf/exceptions.h:26:4: error: #error "The
API defined in this file has been DEPRECATED and will be
>> URL: http://svn.apache.org/r1519866
> >> Log:
> >> QPID-5111: Make library dependencies clearer in build system
> >> - Use -as-needed to link libraries to avoid unnecessary libraries
> >> - Tidyup mess with nss and qpid-proton libraries
> >>
> >
libraries to avoid unnecessary libraries
- Tidyup mess with nss and qpid-proton libraries
Modified:
qpid/trunk/qpid/cpp/bindings/qmf2/examples/cpp/CMakeLists.txt
qpid/trunk/qpid/cpp/examples/messaging/CMakeLists.txt
qpid/trunk/qpid/cpp/src/CMakeLists.txt
qpid/trunk/qpid/cpp/src
- Tidyup mess with nss and qpid-proton libraries
Modified:
qpid/trunk/qpid/cpp/bindings/qmf2/examples/cpp/CMakeLists.txt
qpid/trunk/qpid/cpp/examples/messaging/CMakeLists.txt
qpid/trunk/qpid/cpp/src/CMakeLists.txt
qpid/trunk/qpid/cpp/src/amqp.cmake
qpid/trunk/qpid/cpp/src/qpid
[
https://issues.apache.org/jira/browse/QPID-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke resolved QPID-5028.
---
Resolution: Fixed
Fix Version/s: 0.24
> Qmf2 examples install script er
mmit 1509739 from c...@apache.org in branch 'qpid/branches/0.24'
[ https://svn.apache.org/r1509739 ]
QPID-5028: Qmf2 examples install script error - merge fix to 0.24 release branch
> Qmf2 examples install script error
> --
>
>
0.24.
> Qmf2 examples install script error
> --
>
> Key: QPID-5028
> URL: https://issues.apache.org/jira/browse/QPID-5028
> Project: Qpid
> Issue Type: Bug
> Components: Packaging
mmit 1508967 from c...@apache.org in branch 'qpid/trunk'
[ https://svn.apache.org/r1508967 ]
QPID-5028: Qmf2 examples install script error
Don't try to install files that don't exist.
This patch may be superseded by new CMake files or by the addition of the .sln
and .vcproj th
[
https://issues.apache.org/jira/browse/QPID-5028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725463#comment-13725463
]
Chuck Rolke commented on QPID-5028:
---
The windows installation of the qmf2 example
Chuck Rolke created QPID-5028:
-
Summary: Qmf2 examples install script error
Key: QPID-5028
URL: https://issues.apache.org/jira/browse/QPID-5028
Project: Qpid
Issue Type: Bug
Components
ure Announce - Java QMF2 API Implementation.
>
>
> Key: QPID-3675
> URL: https://issues.apache.org/jira/browse/QPID-3675
> Project: Qpid
> Issue Type: New Feature
>
Qpid 0.20 you would need to use the release 1.3 tarball.
> New Feature Announce - Java QMF2 API Implementation.
>
>
> Key: QPID-3675
> URL: https://issues.apache.org/ji
On 03/26/2013 12:54 PM, Rob Godfrey wrote:
OK... one final question... in the C++ broker, for a ring policy do
acquired but not yet acknowledged messages (e.g. messages that are
currently sitting in a client's prefetch buffer) count towards the limit?
Yes
--
I'll start by saying I also welcome the work fraser has done, and given it
is one of the primary reasons he was given commit rights look forward to it
making its way onto trunk.
On 25 March 2013 20:27, Fraser Adams wrote:
> On 25/03/13 19:47, Rob Godfrey wrote:
>
>> In the meantime have you got
On 26 March 2013 13:49, Gordon Sim wrote:
> On 03/26/2013 12:28 PM, Rob Godfrey wrote:
>
>> Many apologies for my misunderstanding...
>>
>
> No need, I can see where the confusion would arise, hence the
> clarification!
>
>
> In this case there shouldn't be a big barrier to implementing bounded
On 03/26/2013 12:28 PM, Rob Godfrey wrote:
Many apologies for my misunderstanding...
No need, I can see where the confusion would arise, hence the clarification!
In this case there shouldn't be a big barrier to implementing bounded queue
sizes in the same way in the Java Broker.
The questio
On 26 March 2013 12:45, Gordon Sim wrote:
> On 03/25/2013 10:16 PM, Rob Godfrey wrote:
>
>> The implementation of persistence in
>> the C++ broker pretty much forced them to define ring queues.
>>
>
> Actually the introduction of ring queues was not driven by the store at
> all. It came from us
On 03/25/2013 10:16 PM, Rob Godfrey wrote:
The implementation of persistence in
the C++ broker pretty much forced them to define ring queues.
Actually the introduction of ring queues was not driven by the store at
all. It came from use cases where build up of queues beyond a given
point was
On 25 March 2013 23:05, Fraser Adams wrote:
> On 25/03/13 20:38, Rob Godfrey wrote:
>
>>
>> We should definitely try to address the cases where queue arguments simply
>> have different names. Things like ring queues are a little odd. In the
>> C++ broker they make a lot of sense because of the
On 25/03/13 20:38, Rob Godfrey wrote:
We should definitely try to address the cases where queue arguments simply
have different names. Things like ring queues are a little odd. In the
C++ broker they make a lot of sense because of the design of the persistent
store in use.
I'm not sure that it
On Mon, Mar 25, 2013 at 4:45 PM, Rob Godfrey wrote:
> On 25 March 2013 21:32, Rajith Attapattu wrote:
>
> > On Mon, Mar 25, 2013 at 2:50 PM, Rajith Attapattu
> > wrote:
> > > Actually I'd like to take a step back and ask what are our plans for
> > > QMF and management in general.
> > > Fraser, t
On 25/03/13 20:21, Rajith Attapattu wrote:
f management tools that doesn't play nice with both
brokers.
I'm worried about adding another to the mix given that the Java broker
seems to have a different strategy for management.
Well yes and no. From what I've seen the Java broker has a pluggable
; have
> >> email access but no development IT, it'll be good to have a discussion
> on
> >> management in general and what the thinking on the more "strategic"
> picture
> >> is. I think it's a good time to start this discussion, it's prob
On 25 March 2013 21:27, Fraser Adams wrote:
> On 25/03/13 19:47, Rob Godfrey wrote:
>
>> In the meantime have you got a list of all the areas where the Java
>> Broker and C++ broker are incompatible? I'm sure Gordon and I wouldbe
>> very interested in that and would do our utmost to try to narro
Frase
>>
>>
>>
>> On 25/03/13 12:54, Ted Ross wrote:
>>>
>>> Frase,
>>>
>>> Another possibility is qpid/extras/qmf. That's where the Python
>>> implementation is. We've used the extras directory as a place to put more
On 25 March 2013 20:52, Gordon Sim wrote:
> On 03/25/2013 06:32 PM, Fraser Adams wrote:
>
>> If there's strength of feeling that extras is more appropriate then
>> that's fine and I'll be OK with that, but then the location of the ruby
>> stuff seems inconsistent (I'm not knocking the ruby stuff,
gt; general. Rob looks like he might announce some stuff from OASIS on AMQP
> >>> management in the near future, so perhaps the time is ripe to move all
> >>> the
> >>> management stuff into a new space to start the ball rolling on that
> >>> general
> >&
On 25/03/13 19:47, Rob Godfrey wrote:
In the meantime have you got a list of all the areas where the Java
Broker and C++ broker are incompatible? I'm sure Gordon and I wouldbe
very interested in that and would do our utmost to try to narrow that
gap.
Thanks again,
Rob
Hi Rob, I'm afraid that I
ff changing :-/ so I probably won't be able to make
>>> progress for a week or so 'cause I'm just about to go on holiday. I'll
>>> have
>>> email access but no development IT, it'll be good to have a discussion on
>>> management in general and
On 03/25/2013 06:32 PM, Fraser Adams wrote:
If there's strength of feeling that extras is more appropriate then
that's fine and I'll be OK with that, but then the location of the ruby
stuff seems inconsistent (I'm not knocking the ruby stuff, just trying
to figure the most consistent place).
I
So, firstly I want to echo what Gordon has said.
Speaking for myself I am very grateful for the work you have been
doing on the QMF adapter for the Java broker. I can only apologise
for some of the issues that you hve found in terms of
incompatibilities and I thank you for your patience in dealin
On 03/25/2013 07:25 PM, Fraser Adams wrote:
I'd have no problem migrating things to something new (sigh!!) but I
really think that the QMF Management GUI I put together is pretty good
and I had actually just got things working so that I could talk to both
the C++ and Java brokers using both qpid-
rase
On 25/03/13 12:54, Ted Ross wrote:
Frase,
Another possibility is qpid/extras/qmf. That's where the Python
implementation is. We've used the extras directory as a place to put more
layered functionality, or things that might someday become stand-alone
projects.
-Ted
On 03/24/2
t's probably overdue
> given the divergence between the C++ and Java brokers.
>
> Frase
>
>
>
> On 25/03/13 12:54, Ted Ross wrote:
>>
>> Frase,
>>
>> Another possibility is qpid/extras/qmf. That's where the Python
>> implementation is. W
e the Python
implementation is. We've used the extras directory as a place to put
more layered functionality, or things that might someday become
stand-alone projects.
-Ted
On 03/24/2013 03:15 AM, Fraser Adams wrote:
Hello all,
I'm looking to commit the Java QMF2 API, tools an
Hello all,
I'm looking to commit the Java QMF2 API, tools and GUI that I've
hitherto had as tarballs here
https://issues.apache.org/jira/browse/QPID-3675
It's all pretty self-contained and although has dependencies on the
Qpid Java it doesn't impact anything in the main
Hello all,
I'm looking to commit the Java QMF2 API, tools and GUI that I've
hitherto had as tarballs here
https://issues.apache.org/jira/browse/QPID-3675
It's all pretty self-contained and although has dependencies on the Qpid
Java it doesn't impact anything in the
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3675:
---
Attachment: qmf2-v1.3.tar.gz
QMF2 & Qpid GUI Release 1.3
New Features:
* Implemented QMF2 sup
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3675:
---
Attachment: qmf2-v1.2.tar.gz
QMF2 & Qpid GUI Release 1.2
New Features:
* Initial set of QMF Con
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3675:
---
Attachment: qmf2-v1.1.tar.gz
Latest update of the QMF2 library.
Contains fixes to cope with the
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558286#comment-13558286
]
Fraser Adams commented on QPID-3675:
Just for clarity the update is the 501K
ava QMF2 API Implementation.
>
>
> Key: QPID-3675
> URL: https://issues.apache.org/jira/browse/QPID-3675
> Project: Qpid
> Issue Type: New Feature
> Components:
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558284#comment-13558284
]
Fraser Adams commented on QPID-3675:
I've just made a fairly major uplift to
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3675:
---
Attachment: ipod bindings.png
qmf2.tar.gz
> New Feature Announce - Java QMF2
Hi,
its been a little while since i last took a look at QMF2 has the python
library progressed at all beyond the prototype code that i found last year?
Thanks
James
--
View this message in context:
http://old.nabble.com/QMF2-tp34883912p34883912.html
Sent from the Qpid Developers mailing list
ake build puts qpid.pc and qmf2.pc in wrong place
> ---
>
> Key: QPID-4413
> URL: https://issues.apache.org/jira/browse/QPID-4413
> Project: Qpid
> Issue Type: Bug
>
Steve Huston created QPID-4413:
--
Summary: cmake build puts qpid.pc and qmf2.pc in wrong place
Key: QPID-4413
URL: https://issues.apache.org/jira/browse/QPID-4413
Project: Qpid
Issue Type: Bug
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-3675:
--
Assignee: Ted Ross
> New Feature Announce - Java QMF2 API Implementat
[
https://issues.apache.org/jira/browse/QPID-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3696:
---
Attachment: mgmt-agent-qmf2-schema-support.patch
> C++ broker ManagementAgent currently o
C++ broker ManagementAgent currently only supports QMF2 _what = "OBJECT"
queries. This is a patch to add support for OBJECT_ID, SCHEMA_ID and SCHEM
[
https://issues.apache.org/jira/browse/QPID-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fraser Adams updated QPID-3675:
---
Attachment: qmf2.tar.gz
Java QMF2 API Implementation
> New Feature Announce - J
New Feature Announce - Java QMF2 API Implementation.
Key: QPID-3675
URL: https://issues.apache.org/jira/browse/QPID-3675
Project: Qpid
Issue Type: New Feature
Components: Java
+1
On 11/11/2011 10:53 AM, Andrew Stitcher wrote:
On Fri, 2011-11-11 at 15:24 +, Robbie Gemmell wrote:
This kind of thing seems like a good reason to add a CMake build
project to Jenkins (or, you know, just have 1 build system :p) in
addition to the autotools build Keith set up. Any takers?
+20 :-)
> -Original Message-
> From: Cliff Jansen [mailto:cliffjan...@gmail.com]
> Sent: Friday, November 11, 2011 12:02 PM
> To: dev@qpid.apache.org
> Subject: Re: Remove autotools? [Was: Problems building trunk cpp broker
> since this morning - `src/qmf2.pc.in' n
+1
An additional sub-task would be to rework the separate powershell and
sh scripts within cmake/ctest to a single base (python is a likely
candidate), so that contributers don't need to wear multiple hats.
On Fri, Nov 11, 2011 at 7:53 AM, Andrew Stitcher wrote:
> On Fri, 2011-11-11 at 15:24 +00
On Fri, 2011-11-11 at 15:24 +, Robbie Gemmell wrote:
> This kind of thing seems like a good reason to add a CMake build
> project to Jenkins (or, you know, just have 1 build system :p) in
> addition to the autotools build Keith set up. Any takers?
Personally I go for the 1 build system - Cmake
ote:
>> The cmake build failed last night as well... couldn't configure:
>>
>> CMake Error: File /qpidbuilds/trunk/qpid/cpp/src/qmf2.pc.in does not
>> exist.
>> CMake Error at src/CMakeLists.txt:1369 (configure_file):
>> configure_file Problem configur
On Fri, 2011-11-11 at 08:32 -0600, Steve Huston wrote:
> The cmake build failed last night as well... couldn't configure:
>
> CMake Error: File /qpidbuilds/trunk/qpid/cpp/src/qmf2.pc.in does not
> exist.
> CMake Error at src/CMakeLists.txt:1369 (configure_file):
>
1 - 100 of 116 matches
Mail list logo
