Re: Heads Up: Switch over to cmake for Qpid C++ builds

2013-07-25 Thread Robbie Gemmell 
On 24 July 2013 21:35, Andrew Stitcher  wrote:

> On Tue, 2013-07-23 at 20:25 +0100, Robbie Gemmell wrote:
> > On 23 July 2013 19:46, Andrew Stitcher  wrote:
> >
> > > On Tue, 2013-07-23 at 17:13 +0100, Robbie Gemmell wrote:
> > > > It was announced on the user list before 0.22 that we would disable
> the
> > > > automake build by default for 0.24 so that users had to explicitly
> enable
> > > > it (as many people dont read logs for builds which seem to complete
> ok
> > > and
> > > > might miss the deprecation notice), and would thus definitely know
> it was
> > > > being removed entirely in 0.26. Is that happening?
> > >
> > > I must have my fuzzy head on today - I'm sorry I can't parse the
> > > question at the end there.
> > >
> > > Are you asking whether we have disabled autotools by default in 0.24?
> >
> >
> > I was asking if we are planning to do so, as originally said back around
> > March. I know we haven't done it yet as the Jenkins jobs are still using
> it
> > :)
>
> Well, I'd expect the Jenkins trunk jobs to stop working pretty soon now!
> First from requiring the option, then in short order because the entire
> build system has gone!
>
> I don't think Carl has given me credentials yet to help you migrate to
> cmake, do you know any better?
>
> Andrew
>
>
It did indeed fail. I added the new configure option and scheduled a build,
we shall see if that temporarily fixes it (if i did it right :P) once it
gets run.

I havent had a chance to lok at moving it to cmake myself, and I dont know
of any way I can tell whether you have access yet (have you tried logging
in again and seeing if you get the build and configure etc buttons/options
yet?).

Robbie

Re: Heads Up: Switch over to cmake for Qpid C++ builds

2013-07-25 Thread Alan Conway 

On 07/23/2013 11:01 AM, Andrew Stitcher wrote:


As many here will remember we introduced cmake to the C++ build process
when we acquired a working Windows port courtesy of Steve Huston. At the
time (the end of 2008) we discussed having 2 build systems for Qpid C++
and agreed that it was a "Bad Idea".

However for various reasons we are now 5 years later and we are still
using both build systems. The cmake build has now (finally) come to the
point of virtual parity on Unix systems and it is time to remove the
autotools build.

Autotools has been deprecated for a while and has been printing a
warning that it will be removed soon since 0.22.

0.24 will be the last Qpid release that contains the autotools build. I
will be removing all the traces of the autotools build that I know
about/can find this week, so that we have the rest of the 0.25/0.26
development cycle to make sure that we haven't missed anything in the
move.



Hurray! Champagne for all! Let there be dancing in the streets!

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: Review Request 12006: Removal of obsolete/Depracted code

2013-07-25 Thread Alan Conway 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12006/#review23839
---

Ship it!


Great work!

- Alan Conway


On June 20, 2013, 4:10 p.m., Andrew Stitcher wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12006/
> ---
> 
> (Updated June 20, 2013, 4:10 p.m.)
> 
> 
> Review request for qpid.
> 
> 
> Bugs: QPID-4940, QPID-4941 and QPID-4942
> https://issues.apache.org/jira/browse/QPID-4940
> https://issues.apache.org/jira/browse/QPID-4941
> https://issues.apache.org/jira/browse/QPID-4942
> 
> 
> Repository: qpid
> 
> 
> Description
> ---
> 
> This is the outcome of a series of changes to remove much oobsolete and 
> deprecated code in the Qpid tree:
> 
> This removes obsolete example code; obsolete QMFv1 code and examples.
> 
> Finally (as a result of the above) it changes the "exported" installable 
> header files to be a much smaller set that only support the currently 
> supported Qpid APIs.
> 
> See my github repo for a more granular version of this change as it is 
> intended to be committed to the Qpid source tree: 
> https://github.com/astitcher/qpid/commits/remove-old-api
> 
> 
> Diffs
> -
> 
>   /trunk/qpid/cpp/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/Makefile.am 1494712 
>   /trunk/qpid/cpp/bindings/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/bindings/qmf/Makefile.am 1494712 
>   /trunk/qpid/cpp/bindings/qmf/python/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/bindings/qmf/python/Makefile.am 1494712 
>   /trunk/qpid/cpp/bindings/qmf/python/python.i 1494712 
>   /trunk/qpid/cpp/bindings/qmf/python/qmf.py 1494712 
>   /trunk/qpid/cpp/bindings/qmf/ruby/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/bindings/qmf/ruby/Makefile.am 1494712 
>   /trunk/qpid/cpp/bindings/qmf/ruby/qmf.rb 1494712 
>   /trunk/qpid/cpp/bindings/qmf/ruby/ruby.i 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/Makefile.am 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/agent_ruby.rb 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/python_agent.py 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/python_console.py 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/ruby_console.rb 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/ruby_console_test.rb 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/run_interop_tests 1494712 
>   /trunk/qpid/cpp/bindings/qmf/tests/test_base.rb 1494712 
>   /trunk/qpid/cpp/configure.ac 1494712 
>   /trunk/qpid/cpp/examples/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/examples/Makefile.am 1494712 
>   /trunk/qpid/cpp/examples/old_api/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/examples/old_api/Makefile.am 1494712 
>   /trunk/qpid/cpp/examples/old_api/README.verify 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/Makefile.am 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/declare_queues.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/direct_declare_queues.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/direct_direct_producer.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/direct_listener.vcproj 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/direct_producer.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/listener.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/verify 1494712 
>   /trunk/qpid/cpp/examples/old_api/direct/verify.in 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/Makefile.am 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/declare_queues.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/failover_declare_queues.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/failover_replaying_sender.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/failover_resuming_receiver.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/replaying_sender.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/failover/resuming_receiver.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/CMakeLists.txt 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/Makefile.am 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/fanout_fanout_producer.vcproj 
> 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/fanout_listener.vcproj 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/fanout_producer.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/listener.cpp 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/verify 1494712 
>   /trunk/qpid/cpp/examples/old_api/fanout/verify.in 1494712 
>   /trunk/qpid/cpp/examples/old_api/old-examples.sln 1494712 
>   /trunk/qpid/cpp/examples/old_api/pub-sub/CMakeLists.txt 1494712

Re: Review Request 12875: C++ Broker ACL self tests using misguided try-except patterns for signalling self.fail

2013-07-25 Thread Alan Conway 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12875/#review23841
---



trunk/qpid/cpp/src/tests/acl.py


What's wrong with the original code? I've used this pattern myself, often. 
I don't see any benefit to visiting every use of fail() in the tests!!


- Alan Conway


On July 23, 2013, 6:19 p.m., Chug Rolke wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12875/
> ---
> 
> (Updated July 23, 2013, 6:19 p.m.)
> 
> 
> Review request for qpid.
> 
> 
> Bugs: qpid-5010
> https://issues.apache.org/jira/browse/qpid-5010
> 
> 
> Repository: qpid
> 
> 
> Description
> ---
> 
> Acl.py self tests issue self.fail() calls if an expected exception is not 
> thrown. A proposed fix for two patterns is shown in this review.
> 
> Essentially if the expected exception is thrown then pass. If some other 
> exception is thrown then show it's details. If no exception is thrown then 
> issue the self.fail() that was in the try block. Finally, where necessary, 
> run the cleanup handling to recover from the exception.
> 
> 
> Diffs
> -
> 
>   trunk/qpid/cpp/src/tests/acl.py 1506161 
> 
> Diff: https://reviews.apache.org/r/12875/diff/
> 
> 
> Testing
> ---
> 
> There are 222 self.fail() calls that need to be examined and two of them are 
> changed in this review. The rest need scrutiny and when fixed may reveal 
> failures in the code as in QPID-5011.
> 
> 
> Thanks,
> 
> Chug Rolke
> 
>

Re: Review Request 12875: C++ Broker ACL self tests using misguided try-except patterns for signalling self.fail

2013-07-25 Thread Alan Conway 


> On July 25, 2013, 1:54 p.m., Alan Conway wrote:
> > trunk/qpid/cpp/src/tests/acl.py, line 1254
> > 
> >
> > What's wrong with the original code? I've used this pattern myself, 
> > often. I don't see any benefit to visiting every use of fail() in the 
> > tests!!

Just looked at the JIRA: the example there IS wrong, because "catch Exception" 
will catch the exception thrown by fail(). But this code is correct: 
   except qpid.session.SessionException, e
will not catch the exception thrown by fail().


- Alan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/12875/#review23841
---


On July 23, 2013, 6:19 p.m., Chug Rolke wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12875/
> ---
> 
> (Updated July 23, 2013, 6:19 p.m.)
> 
> 
> Review request for qpid.
> 
> 
> Bugs: qpid-5010
> https://issues.apache.org/jira/browse/qpid-5010
> 
> 
> Repository: qpid
> 
> 
> Description
> ---
> 
> Acl.py self tests issue self.fail() calls if an expected exception is not 
> thrown. A proposed fix for two patterns is shown in this review.
> 
> Essentially if the expected exception is thrown then pass. If some other 
> exception is thrown then show it's details. If no exception is thrown then 
> issue the self.fail() that was in the try block. Finally, where necessary, 
> run the cleanup handling to recover from the exception.
> 
> 
> Diffs
> -
> 
>   trunk/qpid/cpp/src/tests/acl.py 1506161 
> 
> Diff: https://reviews.apache.org/r/12875/diff/
> 
> 
> Testing
> ---
> 
> There are 222 self.fail() calls that need to be examined and two of them are 
> changed in this review. The rest need scrutiny and when fixed may reveal 
> failures in the code as in QPID-5011.
> 
> 
> Thanks,
> 
> Chug Rolke
> 
>

[jira] [Commented] (QPID-4835) JMS client is unable to read the application headers of messages sent by the ruby clients

2013-07-25 Thread Darryl L. Pierce (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719671#comment-13719671
 ] 

Darryl L. Pierce commented on QPID-4835:


This doesn't appear to be an issue with the Ruby client, but rather with the 
Java/JMS codebase. I was able to use spout.rb and drain.rb to send and read 
messages with properties, and also the spout and drain C++ examples, 
interchangeable; i.e., C++ spout -> Ruby drain.rb, Ruby spout.rb -> C++ drain, 
Ruby spout.rb -> drain.rb, C++ spout -> drain

But when I used either the C++ spout or Ruby spout examples and then attempted 
to use the Java Drain example, Java failed for either spout example to read any 
properties.

== TESTING ==

>From C++ to Ruby

C++ spout:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P foo=bar

Ruby drain.rb:

mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib drain.rb 
"my-queue"
Message(properties={foo:bar, spout-id:78a019a9-aa2a-436a-9332-62fec8a1464f:0, 
x-amqp-0-10.routing-key:my-queue}, content='')


>From Ruby to C++

Ruby spout.rb:

mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib spout.rb 
-P farke=berry "my-queue;{create:always}"


C++ drain:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/drain "my-queue"
Message(properties={farke:berry, x-amqp-0-10.routing-key:my-queue}, content='')

>From C++ to Java

C++ spout:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P wrinkle=time


Java Drain:

mcpierce@mcpierce-laptop:java 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ java -classpath 
build/scratch/client/example/classes/:lib/required/geronimo-jms_1.1_spec-1.0.jar:build/scratch/client/classes/:build/scratch/common/classes/:build/lib/slf4j-log4j12-1.6.4.jar:build/lib/slf4j-api-1.6.4.jar:build/lib/log4j-1.2.16.jar
 org.apache.qpid.example.Drain "my-queue" | grep Properties
log4j:WARN No appenders could be found for logger 
(org.apache.qpid.client.AMQConnection).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Properties:


> JMS client is unable to read the application headers of messages sent by the 
> ruby clients
> -
>
> Key: QPID-4835
> URL: https://issues.apache.org/jira/browse/QPID-4835
> Project: Qpid
>  Issue Type: Bug
>  Components: Ruby Client
>Affects Versions: 0.20
>Reporter: Petr Matousek
>Assignee: Darryl L. Pierce
>
> I was unable to read the application headers of messages sent by the ruby 
> example client (spout) using the JMS example client.
> ie.
> # cd /usr/lib/ruby/gems/1.8/gems/qpid_messaging-0.20.2/examples
> # ruby spout.rb -P foo=bar q
> # cd /usr/share/doc/qpid-java-0.22/examples
> # ./run_example.sh org.apache.qpid.example.Drain q | grep Properties
> Properties:
> Properties of the received message shall list 'foo = bar'.
> note: JMS client can read application headers of messages sent by c++/python.
> packages used:
> ruby gem: qpid_messaging-0.20.2
> java Drain example from qpid-0.22

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Comment Edited] (QPID-4835) JMS client is unable to read the application headers of messages sent by the ruby clients

2013-07-25 Thread Darryl L. Pierce (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719671#comment-13719671
 ] 

Darryl L. Pierce edited comment on QPID-4835 at 7/25/13 2:58 PM:
-

This doesn't appear to be an issue with the Ruby client, but rather with the 
Java/JMS codebase. I was able to use spout.rb and drain.rb to send and read 
messages with properties, and also the spout and drain C++ examples, 
interchangeable; i.e., C++ spout -> Ruby drain.rb, Ruby spout.rb -> C++ drain, 
Ruby spout.rb -> drain.rb, C++ spout -> drain

But when I used either the C++ spout or Ruby spout examples and then attempted 
to use the Java Drain example, Java failed for either spout example to read any 
properties.

== TESTING ==

>From C++ to Ruby

C++ spout:

| mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P foo=bar

Ruby drain.rb:

| mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib drain.rb 
"my-queue"
| Message(properties={foo:bar, spout-id:78a019a9-aa2a-436a-9332-62fec8a1464f:0, 
x-amqp-0-10.routing-key:my-queue}, content='')


>From Ruby to C++

Ruby spout.rb:

bq. mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib spout.rb 
-P farke=berry "my-queue;{create:always}"


C++ drain:

bq. mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/drain "my-queue"
bq. Message(properties={farke:berry, x-amqp-0-10.routing-key:my-queue}, 
content='')

>From C++ to Java

C++ spout:

bq. mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P wrinkle=time


Java Drain:

bq. mcpierce@mcpierce-laptop:java 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ java -classpath 
build/scratch/client/example/classes/:lib/required/geronimo-jms_1.1_spec-1.0.jar:build/scratch/client/classes/:build/scratch/common/classes/:build/lib/slf4j-log4j12-1.6.4.jar:build/lib/slf4j-api-1.6.4.jar:build/lib/log4j-1.2.16.jar
 org.apache.qpid.example.Drain "my-queue" | grep Properties
bq. log4j:WARN No appenders could be found for logger 
(org.apache.qpid.client.AMQConnection).
bq. log4j:WARN Please initialize the log4j system properly.
bq. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for 
more info.
bq. Properties:

  was (Author: mcpierce):
This doesn't appear to be an issue with the Ruby client, but rather with 
the Java/JMS codebase. I was able to use spout.rb and drain.rb to send and read 
messages with properties, and also the spout and drain C++ examples, 
interchangeable; i.e., C++ spout -> Ruby drain.rb, Ruby spout.rb -> C++ drain, 
Ruby spout.rb -> drain.rb, C++ spout -> drain

But when I used either the C++ spout or Ruby spout examples and then attempted 
to use the Java Drain example, Java failed for either spout example to read any 
properties.

== TESTING ==

>From C++ to Ruby

C++ spout:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P foo=bar

Ruby drain.rb:

mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib drain.rb 
"my-queue"
Message(properties={foo:bar, spout-id:78a019a9-aa2a-436a-9332-62fec8a1464f:0, 
x-amqp-0-10.routing-key:my-queue}, content='')


>From Ruby to C++

Ruby spout.rb:

mcpierce@mcpierce-laptop:examples 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ ruby -I ../lib spout.rb 
-P farke=berry "my-queue;{create:always}"


C++ drain:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/drain "my-queue"
Message(properties={farke:berry, x-amqp-0-10.routing-key:my-queue}, content='')

>From C++ to Java

C++ spout:

mcpierce@mcpierce-laptop:cmake 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ 
./examples/messaging/spout "my-queue;{create:always}" -P wrinkle=time


Java Drain:

mcpierce@mcpierce-laptop:java 
(QPID-4835-JMS-client-is-unable-to-read-app-headers) $ java -classpath 
build/scratch/client/example/classes/:lib/required/geronimo-jms_1.1_spec-1.0.jar:build/scratch/client/classes/:build/scratch/common/classes/:build/lib/slf4j-log4j12-1.6.4.jar:build/lib/slf4j-api-1.6.4.jar:build/lib/log4j-1.2.16.jar
 org.apache.qpid.example.Drain "my-queue" | grep Properties
log4j:WARN No appenders could be found for logger 
(org.apache.qpid.client.AMQConnection).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
Properties:

  
> JMS client is unable to read the application headers of messages sent by

[jira] [Commented] (QPID-5014) Make autotools build require special argument to work

2013-07-25 Thread Alan Conway (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719680#comment-13719680
 ] 

Alan Conway commented on QPID-5014:
---

Reviewed and approved for 0.24

> Make autotools build require special argument to work
> -
>
> Key: QPID-5014
> URL: https://issues.apache.org/jira/browse/QPID-5014
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.24
>
>
> autotools builds have been deprecated and will be removed in 0.26. To make 
> sure that users really notice this we will stop the autotools build from 
> working by default in 0.24.
> It will require the user to specify specifically that they want to use the 
> deprecated build system before autotools builds will run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-5016) Legacy store not correctly initialising rmgr

2013-07-25 Thread Andrew Stitcher (JIRA) 
Andrew Stitcher created QPID-5016:
-

 Summary: Legacy store not correctly initialising rmgr
 Key: QPID-5016
 URL: https://issues.apache.org/jira/browse/QPID-5016
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher


Gcc 4.8.1 found an incorrect memset in legacystore/jrnl/rmgr.cpp, where the an 
aio_cb struct is zeroed using a sizeof aio_cb* rather than aio_cb.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-5017) WinSDK build leaves release executables stranded in \bin directory

2013-07-25 Thread Chuck Rolke (JIRA) 
Chuck Rolke created QPID-5017:
-

 Summary: WinSDK build leaves release executables stranded in \bin 
directory
 Key: QPID-5017
 URL: https://issues.apache.org/jira/browse/QPID-5017
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools
Affects Versions: 0.22
 Environment: windows
Reporter: Chuck Rolke
Assignee: Chuck Rolke


Several new[1] files have been added to C++ install
* qmf-gen
* qpidt
* qpid-ping
* qpid-send 
* qpid-receive
* qpid-topic-listener
* qpid-topic-publisher
* sender
* receiver

But these files are not properly disposed in the WinSDK build process. WinSDK 
separates the debug and release variants into separate subdirectories bin\Debug 
and bin\Release. The files listed above are installed twice to \bin with the 
Release variants overwriting the Debug variants. The final SDK is left with 
only the Release variants sitting in the wrong directory.

These files should be moved into bin\Debug after the debug build and moved 
again into bin\Release after the release build.

[1] 2012-10-22

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5011) C++ Broker ACL allows one connection when user quota is zero

2013-07-25 Thread Ken Giusti (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719843#comment-13719843
 ] 

Ken Giusti commented on QPID-5011:
--

This change looks good!

> C++ Broker ACL allows one connection when user quota is zero
> 
>
> Key: QPID-5011
> URL: https://issues.apache.org/jira/browse/QPID-5011
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.22
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.25
>
>
> If an ACL file has a rule like
> {noformat}
> quota connections 0 user@QPID
> {noformat}
> then the user is still allowed one connection.
> This feature was tested in a self test but the self test did not detect that 
> the feature was broken. See QPID-5010.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5011) C++ Broker ACL allows one connection when user quota is zero

2013-07-25 Thread Justin Ross (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719845#comment-13719845
 ] 

Justin Ross commented on QPID-5011:
---

Reviewed by Ken.  Approved for 0.24.

> C++ Broker ACL allows one connection when user quota is zero
> 
>
> Key: QPID-5011
> URL: https://issues.apache.org/jira/browse/QPID-5011
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.22
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.25
>
>
> If an ACL file has a rule like
> {noformat}
> quota connections 0 user@QPID
> {noformat}
> then the user is still allowed one connection.
> This feature was tested in a self test but the self test did not detect that 
> the feature was broken. See QPID-5010.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5011) C++ Broker ACL allows one connection when user quota is zero

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719880#comment-13719880
 ] 

ASF subversion and git services commented on QPID-5011:
---

Commit 1507084 from c...@apache.org in branch 'qpid/branches/0'
[ https://svn.apache.org/r1507084 ]

QPID-5011: merge fix to 0.24 branch

> C++ Broker ACL allows one connection when user quota is zero
> 
>
> Key: QPID-5011
> URL: https://issues.apache.org/jira/browse/QPID-5011
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Affects Versions: 0.22
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
> Fix For: 0.25
>
>
> If an ACL file has a rule like
> {noformat}
> quota connections 0 user@QPID
> {noformat}
> then the user is still allowed one connection.
> This feature was tested in a self test but the self test did not detect that 
> the feature was broken. See QPID-5010.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5016) Legacy store not correctly initialising rmgr

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719891#comment-13719891
 ] 

ASF subversion and git services commented on QPID-5016:
---

Commit 1507085 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1507085 ]

QPID-5016: Zero rmgr struct element with correct size.

> Legacy store not correctly initialising rmgr
> 
>
> Key: QPID-5016
> URL: https://issues.apache.org/jira/browse/QPID-5016
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>
> Gcc 4.8.1 found an incorrect memset in legacystore/jrnl/rmgr.cpp, where the 
> an aio_cb struct is zeroed using a sizeof aio_cb* rather than aio_cb.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-5016) Legacy store not correctly initialising rmgr

2013-07-25 Thread Andrew Stitcher (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved QPID-5016.
---

   Resolution: Fixed
Fix Version/s: 0.25

> Legacy store not correctly initialising rmgr
> 
>
> Key: QPID-5016
> URL: https://issues.apache.org/jira/browse/QPID-5016
> Project: Qpid
>  Issue Type: Bug
>  Components: C++ Broker
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
> Fix For: 0.25
>
>
> Gcc 4.8.1 found an incorrect memset in legacystore/jrnl/rmgr.cpp, where the 
> an aio_cb struct is zeroed using a sizeof aio_cb* rather than aio_cb.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-4835) JMS client is unable to read the application headers of messages sent by the ruby clients

2013-07-25 Thread Darryl L. Pierce (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-4835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Darryl L. Pierce updated QPID-4835:
---

Component/s: (was: Ruby Client)
 Java Client

> JMS client is unable to read the application headers of messages sent by the 
> ruby clients
> -
>
> Key: QPID-4835
> URL: https://issues.apache.org/jira/browse/QPID-4835
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Client
>Affects Versions: 0.20
>Reporter: Petr Matousek
>Assignee: Darryl L. Pierce
>
> I was unable to read the application headers of messages sent by the ruby 
> example client (spout) using the JMS example client.
> ie.
> # cd /usr/lib/ruby/gems/1.8/gems/qpid_messaging-0.20.2/examples
> # ruby spout.rb -P foo=bar q
> # cd /usr/share/doc/qpid-java-0.22/examples
> # ./run_example.sh org.apache.qpid.example.Drain q | grep Properties
> Properties:
> Properties of the received message shall list 'foo = bar'.
> note: JMS client can read application headers of messages sent by c++/python.
> packages used:
> ruby gem: qpid_messaging-0.20.2
> java Drain example from qpid-0.22

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5014) Make autotools build require special argument to work

2013-07-25 Thread Justin Ross (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719950#comment-13719950
 ] 

Justin Ross commented on QPID-5014:
---

Reviewed by Alan.  Approved for 0.24.

> Make autotools build require special argument to work
> -
>
> Key: QPID-5014
> URL: https://issues.apache.org/jira/browse/QPID-5014
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.24
>
>
> autotools builds have been deprecated and will be removed in 0.26. To make 
> sure that users really notice this we will stop the autotools build from 
> working by default in 0.24.
> It will require the user to specify specifically that they want to use the 
> deprecated build system before autotools builds will run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4640) Deprecate autoconf/automake build system.

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720006#comment-13720006
 ] 

ASF subversion and git services commented on QPID-4640:
---

Commit 1507112 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1507112 ]

QPID-4640: QPID-3633: Remove autotools build from qpid C++ source tree

> Deprecate autoconf/automake build system.
> -
>
> Key: QPID-4640
> URL: https://issues.apache.org/jira/browse/QPID-4640
> Project: Qpid
>  Issue Type: Improvement
>  Components: Build Tools
>Affects Versions: 0.20
>Reporter: Alan Conway
>Assignee: Andrew Stitcher
>
> Deprecate the automake build system in favour of the cmake build system. The 
> cmake system has been in use for several years now, and is more portable 
> (supports windows). Having two redundant systems is a source of confusion and 
> errors. 
> - Update docs (INSTALL, README, release notes etc.) to use cmake
> - The configure script will fail by default with a deprecation message.
> - Users can still use automake by doing "configure --use-deprecated=yes"
> We will keep both systems working for this release, and remove the automake 
> system in a subsequent release. This gives us at least one release cycle with 
> both systems available so we can fix any bugs/deficiencies found in the cmake 
> system as users switch from automake.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-3633) Make cmake the primary build tool for the cpp tree

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720007#comment-13720007
 ] 

ASF subversion and git services commented on QPID-3633:
---

Commit 1507112 from [~astitcher] in branch 'qpid/trunk'
[ https://svn.apache.org/r1507112 ]

QPID-4640: QPID-3633: Remove autotools build from qpid C++ source tree

> Make cmake the primary build tool for the cpp tree
> --
>
> Key: QPID-3633
> URL: https://issues.apache.org/jira/browse/QPID-3633
> Project: Qpid
>  Issue Type: Improvement
>  Components: Build Tools
>Affects Versions: 0.19
>Reporter: Justin Ross
>Assignee: Andrew Stitcher
>
> This will serve as a tracker for the steps remaining to prepare cmake to be 
> our primary (and very probably only) build tool for the cpp tree.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-5014) Make autotools build require special argument to work

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720046#comment-13720046
 ] 

ASF subversion and git services commented on QPID-5014:
---

Commit 1507121 from [~astitcher] in branch 'qpid/branches/0'
[ https://svn.apache.org/r1507121 ]

QPID-5014: Require "--enable-deprecated-autotools" to use autotools

> Make autotools build require special argument to work
> -
>
> Key: QPID-5014
> URL: https://issues.apache.org/jira/browse/QPID-5014
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.24
>
>
> autotools builds have been deprecated and will be removed in 0.26. To make 
> sure that users really notice this we will stop the autotools build from 
> working by default in 0.24.
> It will require the user to specify specifically that they want to use the 
> deprecated build system before autotools builds will run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-4989) Java performance tests - add documentation

2013-07-25 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/QPID-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720047#comment-13720047
 ] 

ASF subversion and git services commented on QPID-4989:
---

Commit 1507122 from [~philharveyonline] in branch 'qpid/trunk'
[ https://svn.apache.org/r1507122 ]

QPID-4989: moved Java perf test README into a docbook so it can be published if 
required.

> Java performance tests - add documentation
> --
>
> Key: QPID-4989
> URL: https://issues.apache.org/jira/browse/QPID-4989
> Project: Qpid
>  Issue Type: Task
>  Components: Documentation, Java Performance Tests
>Reporter: Philip Harvey
>Assignee: Robbie Gemmell
>Priority: Minor
> Attachments: 
> 0001-QPID-4989-moved-Java-perf-test-README-into-a-docbook.patch
>
>
> The Java performance tests in java/perftests have a brief README file but 
> would benefit from better documentation so the tests could be run by people 
> other than the authors of the framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4640) Deprecate autoconf/automake build system.

2013-07-25 Thread Andrew Stitcher (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved QPID-4640.
---

   Resolution: Fixed
Fix Version/s: 0.25

> Deprecate autoconf/automake build system.
> -
>
> Key: QPID-4640
> URL: https://issues.apache.org/jira/browse/QPID-4640
> Project: Qpid
>  Issue Type: Improvement
>  Components: Build Tools
>Affects Versions: 0.20
>Reporter: Alan Conway
>Assignee: Andrew Stitcher
> Fix For: 0.25
>
>
> Deprecate the automake build system in favour of the cmake build system. The 
> cmake system has been in use for several years now, and is more portable 
> (supports windows). Having two redundant systems is a source of confusion and 
> errors. 
> - Update docs (INSTALL, README, release notes etc.) to use cmake
> - The configure script will fail by default with a deprecation message.
> - Users can still use automake by doing "configure --use-deprecated=yes"
> We will keep both systems working for this release, and remove the automake 
> system in a subsequent release. This gives us at least one release cycle with 
> both systems available so we can fix any bugs/deficiencies found in the cmake 
> system as users switch from automake.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-5014) Make autotools build require special argument to work

2013-07-25 Thread Andrew Stitcher (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher resolved QPID-5014.
---

Resolution: Fixed

> Make autotools build require special argument to work
> -
>
> Key: QPID-5014
> URL: https://issues.apache.org/jira/browse/QPID-5014
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.24
>
>
> autotools builds have been deprecated and will be removed in 0.26. To make 
> sure that users really notice this we will stop the autotools build from 
> working by default in 0.24.
> It will require the user to specify specifically that they want to use the 
> deprecated build system before autotools builds will run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-5014) Make autotools build require special argument to work

2013-07-25 Thread Andrew Stitcher (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Stitcher updated QPID-5014:
--

Status: Ready To Review  (was: In Progress)

> Make autotools build require special argument to work
> -
>
> Key: QPID-5014
> URL: https://issues.apache.org/jira/browse/QPID-5014
> Project: Qpid
>  Issue Type: Bug
>  Components: Build Tools
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Blocker
> Fix For: 0.24
>
>
> autotools builds have been deprecated and will be removed in 0.26. To make 
> sure that users really notice this we will stop the autotools build from 
> working by default in 0.24.
> It will require the user to specify specifically that they want to use the 
> deprecated build system before autotools builds will run.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-4989) Java performance tests - add documentation

2013-07-25 Thread Philip Harvey (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Harvey reassigned QPID-4989:
---

Assignee: Philip Harvey  (was: Robbie Gemmell)

> Java performance tests - add documentation
> --
>
> Key: QPID-4989
> URL: https://issues.apache.org/jira/browse/QPID-4989
> Project: Qpid
>  Issue Type: Task
>  Components: Documentation, Java Performance Tests
>Reporter: Philip Harvey
>Assignee: Philip Harvey
>Priority: Minor
> Attachments: 
> 0001-QPID-4989-moved-Java-perf-test-README-into-a-docbook.patch
>
>
> The Java performance tests in java/perftests have a brief README file but 
> would benefit from better documentation so the tests could be run by people 
> other than the authors of the framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-4989) Java performance tests - add documentation

2013-07-25 Thread Philip Harvey (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-4989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Harvey resolved QPID-4989.
-

   Resolution: Fixed
Fix Version/s: 0.25

I checked the patch again, satisfied myself that it's ok, and committed it.

> Java performance tests - add documentation
> --
>
> Key: QPID-4989
> URL: https://issues.apache.org/jira/browse/QPID-4989
> Project: Qpid
>  Issue Type: Task
>  Components: Documentation, Java Performance Tests
>Reporter: Philip Harvey
>Assignee: Philip Harvey
>Priority: Minor
> Fix For: 0.25
>
> Attachments: 
> 0001-QPID-4989-moved-Java-perf-test-README-into-a-docbook.patch
>
>
> The Java performance tests in java/perftests have a brief README file but 
> would benefit from better documentation so the tests could be run by people 
> other than the authors of the framework.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-5018) Mark deprecated APIs to issue warnings if used by applications.

2013-07-25 Thread Ken Giusti (JIRA) 
Ken Giusti created QPID-5018:


 Summary: Mark deprecated APIs to issue warnings if used by 
applications.
 Key: QPID-5018
 URL: https://issues.apache.org/jira/browse/QPID-5018
 Project: Qpid
  Issue Type: Bug
  Components: C++ Broker, C++ Client, Qpid Managment Framework
Affects Versions: 0.24
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Blocker
 Fix For: 0.24


QPID-4940 and QPID-4942 will remove public APIs on release of 0.26.

For 0.24, it would be ideal to add some sort of notification when applications 
are built against these interfaces.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-5019) Add flag to distinguish QMF v1 events

2013-07-25 Thread Ken Giusti (JIRA) 
Ken Giusti created QPID-5019:


 Summary: Add flag to distinguish QMF v1 events
 Key: QPID-5019
 URL: https://issues.apache.org/jira/browse/QPID-5019
 Project: Qpid
  Issue Type: Bug
  Components: Qpid Managment Framework
Affects Versions: 0.22
Reporter: Ken Giusti
Assignee: Ken Giusti
 Fix For: 0.24


Older brokers issue two QMF events - one per format - per incident.  Add flag 
to Event class to help distinguish (consistent with ObjectId class).



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-5019) Add flag to distinguish QMF v1 events

2013-07-25 Thread Ken Giusti (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti updated QPID-5019:
-

Description: 
Older brokers issue two QMF events - one per format - per incident.  Add flag 
to Event class to help distinguish (consistent with ObjectId class).

Bug discovered by Bill Freeman.


  was:
Older brokers issue two QMF events - one per format - per incident.  Add flag 
to Event class to help distinguish (consistent with ObjectId class).




> Add flag to distinguish QMF v1 events
> -
>
> Key: QPID-5019
> URL: https://issues.apache.org/jira/browse/QPID-5019
> Project: Qpid
>  Issue Type: Bug
>  Components: Qpid Managment Framework
>Affects Versions: 0.22
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.24
>
>
> Older brokers issue two QMF events - one per format - per incident.  Add flag 
> to Event class to help distinguish (consistent with ObjectId class).
> Bug discovered by Bill Freeman.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-5019) Add flag to distinguish QMF v1 events

2013-07-25 Thread Ken Giusti (JIRA) 

 [ 
https://issues.apache.org/jira/browse/QPID-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti updated QPID-5019:
-

Attachment: qpid-5019.patch

Fix based on proposal by Bill.

> Add flag to distinguish QMF v1 events
> -
>
> Key: QPID-5019
> URL: https://issues.apache.org/jira/browse/QPID-5019
> Project: Qpid
>  Issue Type: Bug
>  Components: Qpid Managment Framework
>Affects Versions: 0.22
>Reporter: Ken Giusti
>Assignee: Ken Giusti
> Fix For: 0.24
>
> Attachments: qpid-5019.patch
>
>
> Older brokers issue two QMF events - one per format - per incident.  Add flag 
> to Event class to help distinguish (consistent with ObjectId class).
> Bug discovered by Bill Freeman.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org