RE: Cdash scoreboard available for qpid dev use

2009-07-01 Thread Steve Huston
Hi Andrew, > On Wed, 2009-07-01 at 11:43 -0400, Steve Huston wrote: > > Hi folks, > > > > As part of migrating the Qpid build system to Cmake, I've > also set up > > a Cdash dashboard to hold build results. The dashboard gives a good > > overall view of the health of the builds; can keep track o

Re: Cdash scoreboard available for qpid dev use

2009-07-01 Thread Andrew Stitcher
On Wed, 2009-07-01 at 11:43 -0400, Steve Huston wrote: > Hi folks, > > As part of migrating the Qpid build system to Cmake, I've also set up > a Cdash dashboard to hold build results. The dashboard gives a good > overall view of the health of the builds; can keep track of which > builds are workin

Cdash scoreboard available for qpid dev use

2009-07-01 Thread Steve Huston
Hi folks, As part of migrating the Qpid build system to Cmake, I've also set up a Cdash dashboard to hold build results. The dashboard gives a good overall view of the health of the builds; can keep track of which builds are working and help show some history when they don't. The dashboard is ava

[jira] Resolved: (QPID-1963) segfault in TopicExchange::isBound()

2009-07-01 Thread Gordon Sim (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-1963. -- Resolution: Fixed > segfault in TopicExchange::isBound() > > >

Re: testAlertingReallyWorks?

2009-07-01 Thread Aidan Skinner
On Tue, Jun 30, 2009 at 11:52 AM, Marnie McCormack wrote: > Fortunately or unfortunately, It fails pretty regularly so I'm betting you > get to raise the JIRA ! I'm re-enabling this. Yell if you see it fail please. :) - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.

[jira] Updated: (QPID-1963) segfault in TopicExchange::isBound()

2009-07-01 Thread Gordon Sim (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-1963: - Attachment: TopicExchange.patch Patch represeting the fix, now committed on trunk as r790164. > segfault

make distcheck

2009-07-01 Thread Ján Sáreník
Hi there! Just an update, since two patches - one by aconway (789726), the other (and equally important) by tross (789773) - I can already make distcheck when bootstrapping using last autotools on non-RHEL Linux distribution. Thanks for fixing that! Not wanting to raise following much, but I ha

[jira] Resolved: (QPID-1964) bin/release.sh --help does not work

2009-07-01 Thread Aidan Skinner (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1964. - Resolution: Fixed Fix Version/s: (was: 0.5) 0.6 Assignee: Ai

Re: RFC: Ivy Integration (Was RFC: Maven and the Java Build)

2009-07-01 Thread Bryan Kearney
Aidan Skinner wrote: On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney wrote: Taking what Aiden suggested. Here is a first cut at ivy integration. What this does is: 1) Require that every module have an ivy.xml file which is contains all the dependencies. 2) Defines a depVersions.properties file

Re: License question

2009-07-01 Thread Justin Erenkrantz
On Mon, Jun 29, 2009 at 2:30 PM, Ted Ross wrote: > I would like to add a new m4 macro definition (AC_PROG_SWIG) to the CPP > build directory but it has the following license text.  I understand that > GPLv2 is not compatible with the Apache license but I don't know if the > stated exceptions make i

Re: C++ Broker: segfault in TopicExchange::isBound()

2009-07-01 Thread Gordon Sim
rsprin...@mail.etinternational.com wrote: All, We've been using Qpid M4 and 0.5 internally, both with C++, and have been seeing occasional segfaults within the broker. They all seem to occur inside TopicExchange::isBound() (the one with 3 parameters, not 2). Looking at the access patterns in th

[jira] Created: (QPID-1964) bin/release.sh --help does not work

2009-07-01 Thread Jan Sarenik (JIRA)
bin/release.sh --help does not work --- Key: QPID-1964 URL: https://issues.apache.org/jira/browse/QPID-1964 Project: Qpid Issue Type: Bug Components: Build Tools Affects Versions: M4

[jira] Updated: (QPID-1964) bin/release.sh --help does not work

2009-07-01 Thread Jan Sarenik (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Sarenik updated QPID-1964: -- Attachment: 0001-Make-release.sh-help-work.patch Patch > bin/release.sh --help does not work >

[jira] Created: (QPID-1963) segfault in TopicExchange::isBound()

2009-07-01 Thread Gordon Sim (JIRA)
segfault in TopicExchange::isBound() Key: QPID-1963 URL: https://issues.apache.org/jira/browse/QPID-1963 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.5

Re: RFC: Ivy Integration (Was RFC: Maven and the Java Build)

2009-07-01 Thread Aidan Skinner
On Mon, Jun 29, 2009 at 8:36 PM, Bryan Kearney wrote: > Taking what Aiden suggested. Here is a first cut at ivy integration. What > this does is: > > 1) Require that every module have an ivy.xml file which is contains all the > dependencies. > 2) Defines a depVersions.properties file at the root p