Night-Config is divided into several gradle modules: the core modules, plus one module per configuration language.

If you only work in memory, you only need the core module. However, if you want to read and write config files, you also need the module(s) corresponding to your config language: json, toml, hocon, yaml. Note that those modules automatically include the core.

Simply add the module(s) you need, for instance toml, as a dependency from Maven Central.

repositories {
    mavenCentral()
}
dependencies {
    compile 'com.electronwill.night-config:toml:3.6.0'
}

<dependency>
    <groupId>com.electronwill.night-config</groupId>
    <artifactId>toml</artifactId>
    <version>3.6.0</version>
</dependency>

object yourModule extends ScalaModule {
  def ivyDeps = Agg(ivy"com.electronwill.night-config:toml:3.6.0")
}

Older versions of Android don't provide the packages java.util.function and java.nio.file, which NightConfig heavily uses. If you encounter issues with the NightConfig on android, you can use the special version that I've made for you: in your dependencies' declaration, simply append _android at the end of the NightConfig modules.

Example (gradle):

repositories {
    mavenCentral()
}
dependencies {
    compile 'com.electronwill.night-config:toml_android:3.6.0'
    compile 'com.electronwill.night-config:json_android:3.6.0'
}

When using core_android or any of the *_android NightConfig module, most of the features should work just as usual. Here are the known limitations: