Date
1 - 3 of 3
Getting a bridge build version
|
Mark Spielman
I’m interested in any best practices for getting a build version to report as part of the bridgeImpl->bridgeGetVersion() method. I’ve found what looks to be a reasonable version in the file: mama/c_cpp/config.h. I believe this is what AVIS is using. In OpenMAMA 1.1 it’s currently set to:
/* Version number of package */ #define VERSION "5.0.3rc11"
Or it seems I could just reuse the version from mama/c_cpp/c/src/c/mama/version.h as the equivalent of a bridge build version. Any suggestions? I’d like to be able to track a version that identifies a particular build of bridge code to correlate this for bug tracking.
Cheers, Mark
Mark Spielman Development Lead, Solace Systems Professional Services
|
|
|
|
Michael Schonberg <mschonberg@...>
On 03/27/2012 01:12 PM, Mark Spielman wrote:
I'm interested in any best practices for getting a build version to report as part of the bridgeImpl->bridgeGetVersion() method. I've found what looks to be a reasonable version in the file: mama/c_cpp/config.h. I believe this is what AVIS is using. In OpenMAMA 1.1 it's currently set to:It is largely up to the bridge implementor; however, it makes sense to identify both the version of the bridge code and the underlying middleware if it is available. /* Version number of package */Avis does not provide version information through the API so the implementor simply used the MAMA version that was current at the time. Future releases of the Avis bridge will return "not implemented" for this method. Or it seems I could just reuse the version from mama/c_cpp/c/src/c/mama/version.h as the equivalent of a bridge build version. Any suggestions? I'd like to be able to track a version that identifies a particular build of bridge code to correlate this for bug tracking.Regards, -Mike |
|
|
|
Mark Spielman
Mike,
toggle quoted message
Show quoted text
I believe it makes most sense for me to use the mama/version.h as it seems to be the correct place to get version information. One follow on question. Why even in the tar package I downloaded from OpenMAMA for 1.1 is the following still present in mama/version.h. #define MAMA_VERSION "openmama DEVRELEASE.." And this is the value I get when I print the global mama_version. To me this should be set to something like 5.0.3rc11 which would be the concat of: #define MAMA_VERSION_MAJOR 5 #define MAMA_VERSION_MINOR 0 #define MAMA_VERSION_RELEASE 3rc11 Cheers, Mark -----Original Message-----
From: Michael Schonberg [mailto:mikeschonberg@...] On Behalf Of Michael Schonberg Sent: Tuesday, March 27, 2012 5:00 PM To: Mark Spielman Cc: openmama-dev@... Subject: Re: [Openmama-dev] Getting a bridge build version On 03/27/2012 01:12 PM, Mark Spielman wrote: I'm interested in any best practices for getting a build version to report as part of the bridgeImpl->bridgeGetVersion() method. I've found what looks to be a reasonable version in the file: mama/c_cpp/config.h. I believe this is what AVIS is using. In OpenMAMA 1.1 it's currently set to:It is largely up to the bridge implementor; however, it makes sense to identify both the version of the bridge code and the underlying middleware if it is available. /* Version number of package */Avis does not provide version information through the API so the implementor simply used the MAMA version that was current at the time. Future releases of the Avis bridge will return "not implemented" for this method. Or it seems I could just reuse the version from mama/c_cpp/c/src/c/mama/version.h as the equivalent of a bridge build version. Any suggestions? I'd like to be able to track a version that identifies a particular build of bridge code to correlate this for bug tracking.Regards, -Mike |
|
|