[2.1 scala test] play.api.test.FakeApplication doesn't seem to work in combination with composite play project

40 views
Skip to first unread message

Joost de Vries

unread,
Oct 14, 2013, 8:10:51 AM10/14/13
to play-fr...@googlegroups.com
I've got a Play 2.1.x application that is broken up in 3 subprojects and a root aggregate project.
It seems that FakeApplication doesn't find the application.conf file.
I've tried using sbt keys in the play project to see if I can setup the application.conf location correctly. But so far that hasn't worked.

My question is twofold:
a: is this an issue with play 2.1.x and test specs?
b: how can I make the FakeApplication find the application.conf file?

My project is structured as follows:
web/          <--  Play project
web/conf/application.conf
web/app/...
[etc]
core/       
[etc]
project/Build.scala

We use an overall sbt 'root' project that is an sbt aggregate of the other projects.

The problem we're encountering is that during running of our Play specs2 unittest the Play.current.configuration is not filled with the content of our application.conf file

Thank you for your help.
Reply all
Reply to author
Forward
0 new messages