The fix for #195 adds a user-agent string based on the Maven package version. If someone builds the SDK as a plain Java project (for example, in Eclipse, not through Maven), the Maven version info is missing and the user-agent uses "unknown" as the version number.
Should we add the version number to the user-agent code, so it is used no matter how the SDK is built?
- Pro: We tell customers that they can either use the Maven project or build themselves from project. If we put the version in the code, we will get metrics no matter how customers consume the SDK.
- Con: Yet another version number that we have to update. But that can be mitigated by our release checklist.
The fix for #195 adds a user-agent string based on the Maven package version. If someone builds the SDK as a plain Java project (for example, in Eclipse, not through Maven), the Maven version info is missing and the user-agent uses "unknown" as the version number.
Should we add the version number to the user-agent code, so it is used no matter how the SDK is built?