Morning all, I'm sure many of you are aware, but a number of mailing lists have recently been impacted by problems as a result of Yahoo (and potentially others) enforcing stricter DMARC policies. The

Hey Guy, The standard should be too follow the naming convention produced by Scons – this also matches with the Enterprise MAMA builds, so is what most existing OpenMAMA clients expect. I've

Hello, I have an issue compiling the common, commoncpp, mamac, mamacpp. The issue is repeating in Visual Studio for all of them, so I'll use only the commonc issue. Basically

TESTING - Attached test app will show memory leak on windows with old version and none in new version. Running mamalisten with stats enabled will show multiple queues with same name on old

TESTING - Using attached test application the previous verison will log errors, and now the new version will log at level finest. From cddfb49afd15897c529f7f882ae4feb196dd69c4 Mon Sep 17

TESTING - To test this simply try taking a new build and in the <install>/examples/mama/c try setting a different compiler in your environment and then try recompiling something like mamalistenc. To

TESTING – Test by putting activate call in the onError callback. A timeout event will cause an error in the activate. Putting deactivate / activate call in the onMsg will give also cause an

TESTING – I have attached modified versions of mamapublisherc & secstatuslisten.cpp for testing of this issue. The publisher has been modified to now include commandline parameters for both the

Good stuff. We're planning to do a 2.3.1 release in the next few weeks so those changes will be in that versioned release. Glenn From: Guy <guy.tal@...> Date: Thursday, 8 May 2014 09:48 To: Damian

Hi Damian Building mamacpp from next-branch worked perfectly out of the box. Many thanks. Guy On 5/8/2014 10:07 AM, Damian Maguire wrote:

Hey Guy, Thanks for raising this. From a glance at the logs, I assume you're running against 2.3.0. Can you give the HEAD of the next branch a try and see if it resolves your issues - Frank (cc'd)

Hi, I have an issue building the mamacpp project using Visual Studio 2010 and 2012. The configuration is in Win32 Debug and Release. In both cases I compile commonc, commoncpp, mamac and then

Hey Daniel, I haven't taken a look at OpenJDK 1.8 at all yet to be honest, though it's certainly something I'm interested in getting to. I believe there are a few others in the community who have

Yeah, I've been aware of this particular issue for a while, it just hasn't crept up my priority list to deal with it yet. As before, if you want to raise a bugzilla ticket, we can track it there and

Thanks for raising this Daniel, I can see the issue you're talking about, and it appears to be an issue with the way SCons builds it's shared libraries. It'll probably require a bit more digging on my

Hey Daniel, Yeah, we left the autotools stuff around while SCons gets a chance to bed in, just in case we hit some of the sort of problems you've been noticing. At present I don't think there's been

I notice bits of the autotools build system are still present in 2.3.x. Are they still supported in any sense? Are there new source files or build tasks that are described in SCons but not in the

Hey Daniel, Thanks for highlighting that one Daniel. Should be fixed on next. Cheers, D On Sat, May 3, 2014 at 7:22 AM, Daniel Pocock <daniel@...> wrote:

Thanks for highlighting that Daniel, I'll take a look and make sure we fix this for future packages. Cheers, Damian On Sat, May 3, 2014 at 7:16 AM, Daniel Pocock <daniel@...> wrote:

Okay. I'll fix those straight away. I've created one, mcpierce-guest, and would like to use that to track the packaging changes. Excellent! Thank you. So, just to clarify for myself given the