Some changes have just been added to the origin/next branch! [fquinn.ni] Added lex option to allow optional tool

Some changes have just been added to the origin/next branch! [fquinn.ni] [COMMON] Enhancements to support

Huzzah! The first of many I hope! :) Good hunting! Cheers, Frank

Thank you, Frank. My first commit to OpenMAMA hooray! :) 16.11.2017, 21:57, "Frank Quinn" <fquinn.ni@...>:

Hi Yury, This was actually part of why I recently introduced CI for jni - we didn't spot this until it was too late. The short answer is that since its usually a compile time dependency, its so

Thanks Victor - just merged those changes into next. Comprehensive detail in there too - it was much appreciated. Cheers, Frank

Some changes have just been added to the origin/next branch! [fquinn.ni] Fixed few crashes when calling Mama.loadPayloadBridge of Java

Hey guys, I've fixed few JVM crashes in mamajni and have created a pull request: https://github.com/OpenMAMA/OpenMAMA/pull/333 Could someone have a look?

Classification: Public Hi team, We found that Java publishing was broken when onSuccess event was introduced. The problem is here - mamapublisherjni.c, function

Hi Folks, As part of the last round of integration testing prior to the last release, we noticed that Java and C# builds were actually broken and had to be fixed fairly last-minute. To prevent this

Some changes have just been added to the origin/next branch! [Frank Quinn] Set build product to mamdaall release_scripts/ci-run.py[Frank Quinn] Fixed bug in java deserialization

Some changes have just been added to the origin/next branch! [noreply] Fixed memory leak in MamaMsgField (#331) mama/c_cpp/src/cpp/mama/MamaMsgField.h mama/c_cpp/src/cpp/MamaMsgField.cpp Results for

Hi Victor, Apologies - yes the website is out of date - I'll update it. We now follow: https://openmama.github.io/openmama_submission_process.html I did raise the PR on your request

Hey Damian, Could you apply the patch? I thought it's official way to contribute changes - it is documented on openmama.org -> Contribute. 08.11.2017, 14:51, "Damian Maguire" <dmaguire@...>:

Hey Victor, In Github projects, forking is generally the best way to work with the project, and is the recommended approach for raising patches for OpenMAMA - you can actually see the forks used by

Hi Frank, I don't know how to make pull requests without forking the project, that's why I sent the patch. Is it possible for you to apply it? Or is it any instruction on how to do pull

Thanks Victor, Yes I can see how that wouldn't have behaved as expected and fix looks sound. Are you going to raise a pull request against the "next" branch for this or do you want me to take it from

Not sure if my previous mail reached the maillist. Adding list admins, sorry if this is inapropriate. --- It is possible to reproduce memory leak using the following: MamaMsgIterator

Classification: Public Thanks for the details guys!

Hi Yury, Yes that method is deprecated because OpenMAMA prefers dynamic loading methods now (so that payloads don't need to be registered in OpenMAMA's core code to load or depend on magic