Changelog History
Page 2
-
v4.0.0.M2 Changes
March 26, 2019🚀 Release Information
-
v4.0.0.M1 Changes
February 19, 2019🚀 Release Information
-
v3.3.11 Changes
October 15, 2019🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/210?closed=1
⬆️ Dependencies upgraded
- 🚀 Spring Boot 1.5.22.RELEASE
- 🚀 Spring Framework 4.3.25.RELEASE
- Tomcat 8.5.43
-
v3.3.10 Changes
May 20, 2019🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/209?closed=1
⬆️ Dependencies upgraded
- GORM 6.1.12
- 🚀 Spring Boot 1.5.21.RELEASE
- 🚀 Spring Framework 4.3.22.RELEASE
- ✅ Grails Testing support 1.1.5
- Tomcat 8.5.35
⬆️ Grails plugins upgraded
- Gorm Hibernate 5 6.1.12
⬆️ Profiles upgraded
- 🌐 Web 3.3.4
-
v3.3.9 Changes
December 04, 2018🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/207?closed=1
- 🚅 Grails-data-mapping: https://github.com/grails/grails-data-mapping/milestone/79?closed=1
- 🚅 Gorm Hibernate 5: https://github.com/grails/gorm-hibernate5/milestone/3?closed=1
⬆️ Dependencies upgraded
- GORM 6.1.11
- 🚀 Spring Boot 1.5.18.RELEASE
- 🚀 Spring Framework 4.3.21.RELEASE
- ✅ Grails Testing support 1.1.5
- Tomcat 8.5.35
⬆️ Grails plugins upgraded
- Gorm Hibernate 5 6.1.11
- Gorm Mongodb 6.1.7
- Gorm Neo4j 6.1.8
- Cache 4.0.1
- Views 1.2.9
⬆️ Profiles upgraded
- Base 3.3.3
- Angular 6.1.0
-
v3.3.8 Changes
August 10, 2018🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/206?closed=1
Notes
🚀 This version was released to resolve an issue with applications created with the CLI that had an invalid Gradle property.
-
v3.3.7 Changes
August 09, 2018🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/205?closed=1
⬆️ Dependencies upgraded
- 🚀 Spring Boot 1.5.15.RELEASE
Known issues
📚 An extra step is now required to allow reloading of plugins in multi project builds. The entire process is described in the documentation. The new step is to supply a Gradle property to the plugin's build. Set
exploded=truein the plugingradle.propertiesto add the exploded artifacts to the classpath. Unfortunately due to how Gradle plugins work, it's not consistently possible to determine this automatically.🆕 Newly created apps have an invalid GORM version of
gormVersion=${datastore.version}set in thegradle.properties. Change it togormVersion=6.1.10.RELEASEto allow it to work again. -
v3.3.6 Changes
June 15, 2018🚀 Release Information
🛠 Issues fixed
- 🚅 Grails-core: https://github.com/grails/grails-core/milestone/204?closed=1
- 🚅 Grails-data-mapping: https://github.com/grails/grails-data-mapping/milestone/78?closed=1
⬆️ Dependencies upgraded
- GORM 6.1.10
- 🚀 Spring Boot 1.5.14.RELEASE
- 🚀 Spring Framework 4.3.18.RELEASE
⬆️ Grails plugins upgraded
- Fields 2.2.8
- Views 1.2.8
⬆️ Profiles upgraded
- React-webpack 1.0.6
Known issues
⬆️ Due to the upgrade to the latest Spring Boot version you may find the following error
Caused by: java.util.zip.ZipException: invalid entry size (expected 4 but got 3 bytes)when executing thebootRepackagetask. Take a look at this issue #11032 (comment)