Why qmf-agent not included in examples build?

I was adding the examples directory to the cmake build today and am wondering about the examples/qmf-agent directory. It appears that it has only a Makefile, but is not included in the Makefile.am processing. Is this on purpose? Should the qmf-agent directory be included in the build going forward?

[jira] Updated: (QPID-1843) Multiple use of single qpid::management::ManagementAgent::Singleton confusing and error-prone

[ https://issues.apache.org/jira/browse/QPID-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated QPID-1843: --- Attachment: embedded-agent.diff This is a patch that removes the Singleton factory in ManagementBroker and sh

[jira] Commented: (QPID-1842) QMF-generated code doesn't export symbols

[ https://issues.apache.org/jira/browse/QPID-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707364#action_12707364 ] Andrew Stitcher commented on QPID-1842: --- I don't think SELinux is supported on Windows

RE: TLS variables in Windows build (WAS: Re: [0.5] RC-1 now available)

Hi David, > sorry.. kind of getting off-topic in the RC-1 thread, > starting a new one. Good idea. > >>> The problem is that there's a common use case that doesn't work > > with > >>> the static libs. If there is a DLL that links with the static > > client > >>> libs, and that DLL is dynamicall

TLS variables in Windows build (WAS: Re: [0.5] RC-1 now available)

sorry.. kind of getting off-topic in the RC-1 thread, starting a new one. Steve Huston wrote: Hi David, Steve Huston wrote: Hi David, From: David Rennalls [mailto:drenna...@gmail.com] ..snip.. I have to use Visual Studio 2005. You are probably going to have problems... I originally start

RE: Making cmake the default (and soon only build) for Windows

> Except for a very small set of issues I believe that the > cmake Win32/VC9 > build is as good or better than the hard coded build with checked in > project files. I agree. > I propose that we remove the .sln and .vcproj files after the weekend > and stop having to maintain 3 different build sy

RE: [0.5] RC-1 now available

Hi David, > Steve Huston wrote: > > Hi David, > > > >> From: David Rennalls [mailto:drenna...@gmail.com] > ..snip.. > >> I have to use Visual Studio 2005. > > > > You are probably going to have problems... I originally started with > > VS2005 ono the original port - it couldn't deal with some

Re: Proposal for a new JMS Destination configuration

On Fri, May 8, 2009 at 10:21 AM, Robert Godfrey wrote: > I think we need clarity about whether we are defining a format for > *JMSDestination* or for some other AMQP abstraction of > consumer/producer/link. I was under the impression it was the former, and wasn't trying to be a one-stop-solutio

Re: Proposal for a new JMS Destination configuration

Robert Godfrey wrote: I think we need clarity about whether we are defining a format for *JMSDestination* or for some other AMQP abstraction of consumer/producer/link. As I understood it, the idea was to try to define JMS Destinations over AMQP in terms of some more general format for configur

Re: Moving QMF to a top-level directory

>> >> Here's the proposed structure: >> >>  qpid/qmf/cpp           - C++ implementation of qmf components >>  qpid/qmf/cpp/bindings  - Wrapped bindings to components (Python, Ruby, >> C#, WCF, etc.) >>  qpid/qmf/python        - Pure Python implementations (for portability) >>  qpid/qmf/java      

Re: Proposal for a new JMS Destination configuration

>> >> I was thinking the format for specifying queue properties would be >> standard across languages regardless of whether the queue declaration is >> separate or nested. >> >> If you're talking about something like this: >> >> dest.D = MyQueue; {auto-create=true, queue-definition={durable=true, .