Re: Running the java tests

Hi Alan, You can use the "test" system property, as described here: http://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html If I remember correctly, the special "pattern" property mentioned you're seeing in the pom is a non-standard one we added to tell JythonTest to run

Testing types in a message

I'm looking (in python first) to encode messages that contain all the different AMQP types. So far I was using the Data class to construct different AMQP data fragments. However I'd like to move towards using a map message as it's more widely decodable. So my question: how do I create a map message

Running the java tests

Anyone know how to run a subset of proton's Java tests? The pom.xml explains how to do it for the jython test but not for other Java tests.

[jira] [Updated] (PROTON-241) proton-c: mark old transport interfaces 'deprecated'

[ https://issues.apache.org/jira/browse/PROTON-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming updated PROTON-241: --- Fix Version/s: 0.5 > proton-c: mark old transport interfaces 'deprecated' > -

[jira] [Created] (PROTON-241) proton-c: mark old transport interfaces 'deprecated'

Ken Giusti created PROTON-241: - Summary: proton-c: mark old transport interfaces 'deprecated' Key: PROTON-241 URL: https://issues.apache.org/jira/browse/PROTON-241 Project: Qpid Proton Issue Type

Re: proton interop tests failed on Jenkins

On Thu, 2013-02-14 at 15:13 +, Phil Harvey wrote: > I notice that the proton-jni Jenkins job has failed: > > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-jni/25/ > > The commit that broke this build was probably this one for PROTON-215, by > aconway: > > "PROTON-215: Add test

[jira] [Commented] (PROTON-238) Initial CTest support

[ https://issues.apache.org/jira/browse/PROTON-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578572#comment-13578572 ] Mary hinton commented on PROTON-238: This will be a nice feature. Visual Studio doesn

[jira] [Commented] (PROTON-222) pn_messenger_send returns before message data has been written to the wire

[ https://issues.apache.org/jira/browse/PROTON-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578563#comment-13578563 ] Ken Giusti commented on PROTON-222: --- Review Board post with proposed fix: https://revie

[jira] [Commented] (PROTON-235) SASL layer can "replicate" inbound SASL frames under some circumstances.

[ https://issues.apache.org/jira/browse/PROTON-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578553#comment-13578553 ] Ken Giusti commented on PROTON-235: --- Link to related Review Board post: https://reviews

proton interop tests failed on Jenkins

I notice that the proton-jni Jenkins job has failed: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-jni/25/ The commit that broke this build was probably this one for PROTON-215, by aconway: "PROTON-215: Add tests to verify AMQP type support for python bindings." http://svn.apache

[jira] [Updated] (PROTON-61) Need a means of specifying and reading connection capabilities & properties

[ https://issues.apache.org/jira/browse/PROTON-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated PROTON-61: -- Assignee: Rafael H. Schloming (was: Rob Godfrey) > Need a means of specifying and reading connectio