Please see Computing Services' blog post for more details
It is worth telling subversion to ignoring the
In the (vi-powered window) put:
Commit this change separately to the initial commit or madness will ensue.
Run the project
play run or
play run --%local where local is the environment setting. Note that you can also use
play id to set a default environment. Default environment is used if you do not specify an environment - basically saves you having to type the
--%local flag. Out of the box default is blank.
Along with all other settings are in
conf/application.conf - environment specific variables are prefixed with the environment name. To use the continuous integration server ensure there is a
Can be found in
After changing routes, need to restart Play.
After changing, need to run
play dependencies to update local modules. If there is ever a problem with this, the dependencies stuff is cached by ivy2. Clear its cache (
~/.ivy2/cache/ on linux) to force it to go back online.
So far we have used the inbuilt CRUD module and a CAS module. Neither work properly under Java5.
Use Fixtures to load a yaml file. So far we have put this file in
conf/ and loaded it into the model using
Note that the yaml file needs to be a particular syntax:
Changing just the labels for listed objects in the Admin screens
Simply modify the toString method for that object.
Changing the field labels for an object
Hiding a field from CRUD
@Hidden annotation (remember to import