We currently use different JSON libraries for the endpoints and the events API. Additionally the reflection used by json4s currently causes exceptions in the events api (see: https://github.com/mesosphere/marathon/issues/646). Another benefit of using play-json exclusively is that we can remove the somewhat verbose code for custom Jackson de/serialization.
We should continue down this path for consistency's sake, but we need to do more thorough testing. The part that we ported for 0.7.6 ended up unintentionally changing the behavior of the REST API.
We currently use different JSON libraries for the endpoints and the events API. Additionally the reflection used by json4s currently causes exceptions in the events api (see: https://github.com/mesosphere/marathon/issues/646). Another benefit of using play-json exclusively is that we can remove the somewhat verbose code for custom Jackson de/serialization.