- Products ProductsLocation Services
Solve complex location problems from geofencing to custom routing
PlatformCloud environments for location-centric solution development, data exchange and visualization
Tracking & PositioningFast and accurate tracking and positioning of people and devices, indoors or outdoors
APIs & SDKsEasy to use, scaleable and flexible tools to get going quickly
Developer EcosystemsAccess Location Services on your favorite developer platform ecosystem
- Documentation
- Pricing
- Resources ResourcesTutorials TutorialsExamples ExamplesBlog & Release Announcements Blog & Release AnnouncementsChangelog ChangelogDeveloper Newsletter Developer NewsletterKnowledge Base Knowledge BaseFeature List Feature ListSupport Plans Support PlansSystem Status System StatusLocation Services Coverage Information Location Services Coverage InformationSample Map Data for Students Sample Map Data for Students
Versioning Scheme
The Data Client Library uses the semantic versioning scheme 2.0.0.
Binary Compatibility
The Data Client Library maintains backwards binary compatibility across versions of modules.
This means that new JAR files are drop in replacements for the older ones as long as your build does not enable the inliner (Scala-only restriction); but not the other way around.
- Binary compatibility is maintained between minor and patch versions
- Binary compatibility is NOT maintained between: major versions
Mixing Module Versions is Not Allowed
Modules that are released together under the Data Client Library project are intended to be upgraded together. For example, it is not allowed to mix client-core module 1.0.0 with data-client of version 1.0.5 even though "Data Client Library 1.0.0" and "Data Client Library 1.0.5" are binary compatible.
This is because modules may have changed internally. For example, a feature in one module may have required changes internally in another module. However, these changes are not part of the public API, so binary compatibility is still maintained.
