Hi James
After some further tidying up, I seem to have fixed the problem of some routes just not working at all. I'm not sure if this was a hangover from upgrading to the RC2 and I was getting something cached from the previous version, but all of the routes seem to be working now.
However, as part of the testing for this, I have found a problem related to the classpath.
If I have the same template/static asset/class in a module, as one in the application (or other module), then there is an inconsistency which version I get. So in Play1, and I would hope this functionality continues, you could have an application overwrite a template from a module. In dev/start mode, this is the case, the application version would be picked up first, replacing the module version.
However when you do a stage/dist, then the classpath must be different, as it is picking up the module version first.
I have created a simple app to demonstrate this:
In dev/start mode, this will give you a page title of "This is the main template from the app" and a white background colour.
In stage/dist mode, you get "This is the main template from module 1", with a yellow background colour.
If I edit the dist/start script to change the classpath order, making the app.jar appear before the module.jar, then this works as expected. Similarly, if I change the order to find module2.jar first, the message changes to "This is the main template from module2" with a green background.
At the very least the classpath should put the application first. I am not sure how you would then determine the priority of the modules. In Play1, this was controlled by the order of module settings in application.conf, but the SBT build script, only specifies dependencies, not any priorities. If there is a way to specify priorities for the classpath, this would be helpful.
I will raise a lighthouse ticket now, as the module taking preference over the app is definitely a bug for me.
thanks
Daryl.