Several users have reported issues with our use of this library (#112 being the latest). A number of frameworks seem to be using various conflicting versions of this library, which causes errors when trying to use Admin SDK in those frameworks. To make matters worse, there's also another different artifact which has the exact same package structure! It is possible to overcome this type of errors by carefully analyzing the dependency tree, and removing any conflicting artifacts. But it still results in a poor first-time user experience. Therefore we should consider using another, less ambiguous JSON library like gson in Admin SDK.
This won't be easy, since a good part of our RTDB JSON support is tied to this library at the moment. Perhaps we can start migrating non-RTDB code first.
Several users have reported issues with our use of this library (#112 being the latest). A number of frameworks seem to be using various conflicting versions of this library, which causes errors when trying to use Admin SDK in those frameworks. To make matters worse, there's also another different artifact which has the exact same package structure! It is possible to overcome this type of errors by carefully analyzing the dependency tree, and removing any conflicting artifacts. But it still results in a poor first-time user experience. Therefore we should consider using another, less ambiguous JSON library like gson in Admin SDK.
This won't be easy, since a good part of our RTDB JSON support is tied to this library at the moment. Perhaps we can start migrating non-RTDB code first.