Releases: grails/grails-core
Grails 3.0.0 M1
1.3.9
Release Information
Grails 2.4.4
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from previous versions and you use the hibernate4 plugin, you will need to update the version in BuildConfig:
runtime ':hibernate4:4.3.6.1' // or ':hibernate:3.6.10.18'
UPDATE: There is a known issue in hibernate4:4.3.6.1 plugin with the auto-timestamping feature. The workaround is to add these dependencies to
BuildConfig.groovy
compile "javax.validation:validation-api:1.1.0.Final"
runtime "org.hibernate:hibernate-validator:5.0.3.Final"
recommended tomcat, asset-pipeline, cache and scaffolding plugin versions for Grails 2.4.x :
build ':tomcat:7.0.55'
compile ':cache:1.1.8'
compile ':scaffolding:2.1.2'
compile ':asset-pipeline:1.9.9'
If you are using MongoDb GORM, the recommended plugin version is 3.0.2 (No updates since Grails 2.4.3)
compile ':mongodb:3.0.2'
updated grails-datastore-test-support
grails-datastore-test-support was updated.
You should use grails-datastore-test-support version 1.0.2-grails-2.4 for Grails 2.4.4.
dependencies {
...
test "org.grails:grails-datastore-test-support:1.0.2-grails-2.4"
...
}
Changes To Forward Method Unit Tests
When unit testing the results of a controller action which invokes a forward, the forwardedUrl property no longer contains a leading /grails or trailing .dispatch.
@TestFor(DemoController)
class DemoControllerSpec extends Specification {
void 'test a forward call'() {
when:
controller.someAction()
then:
// in Grails 2.4.3 this would have been /grails/demo/someDestination.dispatch
response.forwardedUrl == '/demo/someDestination'
}
}
Changes in default maven repository network connections (http-> https)
Grails 2.4.4 will use https by default to access maven repositories.
Jira issue was GRAILS-11631
This only applies to these maven repository aliases you can use in the repositories configuration block with grails.project.dependency.resolver = "maven".
mavenCentral- https://repo1.maven.org/maven2/jcenter- https://jcenter.bintray.comgrailsCentral- https://repo.grails.org/grails/plugins
Grails 2.4.3
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from Grails 2.4.2 and you use the hibernate4 plugin, you will need to update the version in BuildConfig:
runtime ':hibernate4:4.3.5.5' // or ':hibernate:3.6.10.17'
IMPORTANT! Add "flush.mode = 'manual'" setting to hibernate config block in DataSource.groovy file when upgrading. Read the following upgrade notes about this change in auto flushing behaviour.
recommended tomcat, asset-pipeline, cache and scaffolding plugin versions for Grails 2.4.x :
build ':tomcat:7.0.54'
compile ':cache:1.1.7'
compile ':scaffolding:2.1.2'
compile ':asset-pipeline:1.9.6'
If you are using MongoDb GORM, the recommended plugin version is 3.0.2
compile ':mongodb:3.0.2'
updated grails-datastore-test-support
grails-datastore-test-support was updated after releasing Grails 2.4.3 . You should use grails-datastore-test-support version 1.0.1-grails-2.4 for Grails 2.4.3.
dependencies {
...
test "org.grails:grails-datastore-test-support:1.0.1-grails-2.4"
...
}
This contains fixes for the HibernateTestMixin and MongoDbTestMixin support that is available in Grails 2.4.x .
Changes in hibernate4 plugin auto flushing behaviour in 4.3.5.5 plugin version
In previous versions, the hibernate4 plugin's flush mode for the Open Session in View Interceptor (OSIVI) has been always "manual" regardless of the setting defined in hibernate config block's "flush.mode" setting. This has been changed to be consistent with hibernate plugin (Hibernate 3). This makes it easier to port existing applications using the hibernate plugin to hibernate4 plugin.
IMPORTANT! It is recommended to set Hibernate OSIVI flush mode to "manual" for applications that haven't been upgraded from Hibernate 3 plugin. OSIVI flush mode was always "manual" for plugin versions before 4.3.5.5 version.
Add the "flush.mode = 'manual'" setting to the hibernate config block in grails-app/conf/DataSource.groovy file of your application
hibernate {
...
flush.mode = 'manual'
}
It should be noted that the default HibernateTransactionManager switches the flush mode of the current session to AUTO when the transaction starts. This behaviour exists in both Hibernate3 and Hibernate4. The flush mode setting of the OSIVI doesn't have effect in transactional context.
The flush mode setting of the current session gets switched to MANUAL for read-only transactions.
Resetting metaClass changes in unit tests
Grails 2.4.3 changed the way how metaClass changes are resetted between test methods in a single test class. This was a side-effect of fixing GRAILS-11579
Jira issue: GRAILS-11661 metaClass isn't being properly cleaned up after unit test
The current workaround before Grails 2.4.4 is to add the FreshRuntime annotation to each test method in the test class. FreshRuntime annotation is designed to be used at class (type) or method level. However there is a bug GRAILS-11626 in the class level usage which will be fixed for Grails 2.4.4 .
There is a feature request to add a "DirtiesRuntime" annotation which will stop the current running test runtime after running a test method and also clear metaclass changes.
Grails 2.4.2
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from Grails 2.4.0 and you use the hibernate4 plugin, you will need to update the version in BuildConfig:
runtime ':hibernate4:4.3.5.4' // or ':hibernate:3.6.10.16'
recommended tomcat, asset-pipeline and scaffolding plugin versions for Grails 2.4.x :
build ':tomcat:7.0.54'
compile ':cache:1.1.7'
compile ':scaffolding:2.1.2'
compile ':asset-pipeline:1.8.11'
HibernateTestMixin is now available
There are more details about HibernateTestMixin in What's new in Grails 2.4 Guide guide and the updated guide about unit testing domains. There is now real Hibernate GORM available in unit tests when HibernateTestMixin is used. It's backed by Hibernate 4 and an in-memory H2 database.
Support for Maven-style Dependency Management
It is now possible to declare a management block which is equivalent to the dependencyManagement element in a pom.xml file. This allows you to enforce versions, scopes and exclusions for dependencies. Example
management {
dependency "commons-logging:commons-logging:1.1.3"
}
Grails 2.3.11
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from previous versions of Grails 2.3.x and you use the Hibernate plugin, you will need to update the version in BuildConfig:
runtime ':hibernate:3.6.10.16' // ':hibernate4:4.3.5.4' for Hibernate 4
Recommended tomcat, resources, scaffolding and database-migration plugin versions for Grails 2.3.x :
build ':tomcat:7.0.54'
runtime ':resources:1.2.8'
compile ':scaffolding:2.0.3'
runtime ':database-migration:1.4.0'
Note: database-migration 1.4.0 has support for hibernate4 plugin.
v2.4.1
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from Grails 2.4.0 and you use the hibernate4 plugin, you will need to update the version in BuildConfig:
runtime ':hibernate4:4.3.5.4' // or ':hibernate:3.6.10.16'
recommended tomcat, asset-pipeline and scaffolding plugin versions for Grails 2.4.x :
build ':tomcat:7.0.54'
compile ':scaffolding:2.1.1'
compile ':asset-pipeline:1.8.11'
HibernateTestMixin is now available
There are more details about HibernateTestMixin in What's new in Grails 2.4 Guide guide and the updated guide about unit testing domains. There is now real Hibernate GORM available in unit tests when HibernateTestMixin is used. It's backed by Hibernate 4 and an in-memory H2 database.
Support for Maven-style Dependency Management
It is now possible to declare a management block which is equivalent to the dependencyManagement element in a pom.xml file. This allows you to enforce versions, scopes and exclusions for dependencies. Example
management {
dependency "commons-logging:commons-logging:1.1.3"
}
Grails 2.3.10
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from previous versions of Grails 2.3.x and you use the Hibernate plugin, you will need to update the version in BuildConfig:
runtime ':hibernate:3.6.10.16' // ':hibernate4:4.3.5.4' for Hibernate 4
Recommended tomcat, resources, scaffolding and database-migration plugin versions for Grails 2.3.x :
build ':tomcat:7.0.54'
runtime ':resources:1.2.8'
compile ':scaffolding:2.0.3'
runtime ':database-migration:1.4.0'
Note: database-migration 1.4.0 has support for hibernate4 plugin.
v2.3.9
Release Information
Update Notes
Recommended plugin versions
If you are upgrading from previous versions of Grails 2.3.x and you use the Hibernate plugin, you will need to update the version in BuildConfig:
runtime ':hibernate:3.6.10.15' // ':hibernate4:4.3.5.3' for Hibernate 4
Recommended tomcat, resources, scaffolding and database-migration plugin versions for Grails 2.3.x :
build ':tomcat:7.0.52.1'
runtime ':resources:1.2.8'
compile ':scaffolding:2.0.3'
runtime ':database-migration:1.4.0'
Note: database-migration 1.4.0 has support for hibernate4 plugin.