…y supported not specifying the delimiter at all.
…arams (offset and max)
organisation based on the application name. Such a default does mean there's a good chance of conflicts with the project's dependencies. I've hard-coded an organisation of "org.grails.internal". A bit of a hack, but since the organisation is immaterial at that point in the code, it works fine. Hopefully no one will publish JARs in that org!
…' message code with a default of "Loading..."
…operties that have names that begin with "by" (bypassed, etc...)
…perties now does not require a "By" clause behind the boolean property. Publications.findAllPublishedByAuthor(...) has been supported. Now in addition that, Publications.findAllPublished() is supported.
…ate relationships as part of their criteria
interfaces. I tracked this down to some odd behaviour with Groovy, but that behaviour is unlikely to change soon. So, I've added a workaround to GrailsMock just for interfaces. Added a unit test too.
the validation disabled, Grails now flushes the session and notifies ClosureEventTriggeringInterceptor that it shouldn't validate that particular domain instance. If the domain instance changes at a later date, validation will still occur on the next flush. I have added a unit test to cover this behaviour.