It appears that using DefaultApplication in the way presented in this application does not properly load the configuration file. Not sure if this is a bug in Play or just a misuse of the API. Also, I noticed that the DefaultApplication results in a "DefaultGlobal" being used instead of the application's own GlobalSettings which is another potential problem. I might suggest using the pattern suggest by Ivan in the thread: https://groups.google.com/forum/#!topic/play-framework/kI9GWEw44So

Essentially you might want to use StaticApplication rather than DefaultApplication.

Update:
Turns out you have to specify -Dconfig.file=conf/application.conf. The new File("conf/application.conf") argument for DefaultApplication is not related to specifying the app's configuration during runtime but rather appears to be used to specify the application's root path.

Hi James,
For some reason the JAR with the Job class file is not going to target/staged/ but to target/universal/stage/lib/ instead. I suspect this is because I'm using Play 2.2 but I'm not sure.
To make it work I've changed the classpath option on Procfile to:
-cp "target/universal/stage/lib/*"

Hi James,

As you probably already know, Global.onStart() is called both when initializing the Application and the TickJob. I tried to write some code that would check whether it is the main application or the scheduled job that is running by checking the classloader but to no success. It seems like both of them have the same classloader. I've forked your repository and you can find the Global class I've written here: https://github.com/gabrielcs/play2-scheduled-job-demo/blob/master/app/Global.java

This is important since one may want to connect to a cloud database on Global.onStart() only if it's the Application that's being initialized, for example.

Any ideas?