Use ${objenesisVersion} instead of hardcoding the version as 1.4
Use Objenesis 1.4

One place used to use 1.4, the rest used 1.2. This change consistently uses 1.4.
Merge pull request #535 from candrews/ObjenesisConsistency

Objenesis consistency
attempt to fix occasional travis build failures (timeouts)
fix travis build
prevent travis running "./gradlew assemble"
refactor Travis build settings in gradle build
add .travis.yml for 2.3.x branch too
Merge branch '2.3.x' into 2.4.x

Conflicts:
	.travis.yml
	README.md
	build.gradle
tune gradle build test JVM settings
fix travis build
fix failed travis test
Merge branch '2.3.x' into 2.4.x

Conflicts:
	build.gradle
fix merge conflict
GRAILS-11543 - GroovyPageUnitTestMixin.render should respect grails.gsp.view.dir
GRAILS-11543 - The GrailsApplicationAwareBeanPostProcessor is added by the CoreBeansTestPlugin
test that the GrailsApplicationAware post processor is effective for beans registered by a unit test
GRAILS-11663 encoding not passed to InputStreamReader in GrailsIOUtils.copy
GRAILS-11666 - improve binding array of id to a collection of domain objects in a non domain object
GRAILS-11661 - unit test metaclass cleanup issue

This test uses @FreshRuntime to satsify the requirement.  I don't know if we are going to be able to support cleaning up changes between test methods.  One problem with that is trying to roll back changes made while a test method is running that overlap with changes made while setting up the test environment.  When rolling back the changes made while the test method is running, changes made while setting up the test environment would also be rolled back.  We need to decide if it is worth introducing the complexity necessary to support rolling back changes made while test methods are run.  It may be that we just recommend @FreshRuntime for those scenarios.  Pending discussion with the rest of the team.