Our application will be reading configuration files for schedulers. There are different formats we can force our users to use. We've decided our format of choice to be JSON. It is easy to write our models based on it and we have already used libraries to parse the JSON format in the previous chapters of this book. We will be using json4s: https://github.com/json4s/json4s. We have included it using the following lines in our pom.xml file:
<dependency> <groupId>org.json4s</groupId> <artifactId>json4s-native_2.12</artifactId> <version>${json4s.version}</version></dependency><dependency> <groupId>org.json4s</groupId> <artifactId>json4s-jackson_2.12</artifactId> <version>${json4s.version}</version></dependency> ...
