Accepted answer

It looks like I am victim of some strange file system inconsistencies:

  • I am deploying the module to Play's local repository using play publish-locally
  • This same repository is on Eclipse's build path (created with play eclipsify)
  • Sometimes, the Play main application seems to pick up the module's JAR when it's broken somehow


  • close Eclipse
  • deploy the module locally
  • run a clean build of the main application

Using this procedure, the application's configuration works fine.


While looking into this issue, I came across a useful feature of Typesafe's Config library. You can obtain the whole configuration tree including where each entry comes from using the following line of code:

val configDump: String = current.configuration().underlying.root().render()

and e.g. dump this to a file for further analysis.

Related Query

More Query from same tag