{"id":167869,"date":"2025-11-07T12:17:11","date_gmt":"2025-11-07T12:17:11","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/167869\/"},"modified":"2025-11-07T12:17:11","modified_gmt":"2025-11-07T12:17:11","slug":"grails-7-0-now-under-the-apache-software-foundation-delivers-enhancements-for-micronaut-and-gorm","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/167869\/","title":{"rendered":"Grails 7.0, Now Under the Apache Software Foundation, Delivers Enhancements for Micronaut and GORM"},"content":{"rendered":"

The release<\/a> of Apache Grails<\/a> 7.0.0 delivers bug fixes and notable changes such as: the ability to disable Micronaut auto configuration through the Grails plugin; improved reproducibility with implementations of Grails Object Relational Mapper<\/a> (GORM) services; and a temporary removal of the GORM for Neo4J. Grails 7.0 requires a minimal version of JDK 17 (with testing validated up to JDK 21) and compliance with Spring Boot 3.5 and Jakarta EE 10.<\/p>\n

Due to some issues with Micronaut test code coverage, enhancements to the GrailsGradlePlugin<\/a><\/strong> and GrailsExtension<\/a><\/strong> classes provided the ability to use the Grails plugin to disable Micronaut auto configuration so that these issues can be locally debugged.<\/p>\n

Reproducibility issues in Grails Spring Security<\/a> with the second release candidate<\/a> of Grails 7.0.0 caused a random ordering of closures generated for GORM services causing them to be mismatched. This was resolved with changes to the ServiceTransformation<\/a><\/strong> class.<\/p>\n

GORM for Neo4J<\/a> has been temporarily removed until it is compatible with Grails 7.0 or 8.0. This required deleting the implementation of the Neo4jGorm<\/strong> feature from Grails Forge<\/a>, a starter application for building Grails applications, and its associated tests. The GormImpl<\/a><\/strong> enum has also been updated to remove the Neo4j option along with a cleanup of the MongoGormSpec<\/a><\/strong> class to eliminate any references to Neo4j.<\/p>\n

Originally named Groovy on Rails, Grails was co-founded in 2005 by Graeme Rocher<\/a>, Guillaume LaForge<\/a>, Steven Devijver and Dierk K\u00f6nig<\/a> at the now-defunct G2One, an open-source Groovy\/Grails company that provided training, consultancy, support and products around Groovy<\/a> and Grails<\/a>.<\/p>\n

Grails, now known as Apache Grails, had made its way through a number of companies via acquisitions and spin-offs that included: G2One from 2005-2008; SpringSource\/Pivotal from 2008-2015; Object Computing, Inc.<\/a> (OCI) from 2015-2021; the Grails Foundation\/Unity Foundation from 2021-2025; and now the Apache Software Foundation<\/a> (ASF) as of June 2025.<\/p>\n

OCI established<\/a> the Grails Foundation in October 2021 as a not-for-profit company established to advance innovation and adoption of the Grails framework. The foundation oversaw “software roadmap and development, best practices and processes, repository control, documentation and support, and fundraising related to the open source framework.” The foundation received initial funding of $200,000 from OCI for development and evangelism.<\/p>\n

In October 2025, the ASF announced<\/a> that the Grails project, donated to the foundation in June 2025 from OCI, had graduated from an Incubating<\/strong> project to a Top-Level<\/strong> project. The process to ultimately donate Grails was initiated in May 2024 with this open letter<\/a> by Gina Bremehr,<\/a> CEO at OCI, describing a “marked decline in enterprise adoption and commercial investment” in Grails. The fourth milestone release<\/a> of Grails 7.0.0, delivered in June 2025, was the first release under the auspices of the ASF.<\/p>\n

S\u00f8ren Berg Glasius<\/a>, Apache Groovy Project Management Committee Member, describing the incubation to top-level process, told InfoQ:<\/p>\n

<\/p>\n

Grails, with a history spanning nearly two decades, entered the Apache Incubator in 2024 after transitioning to a community-governed, vendor-neutral project. The ASF incubation period was characterized by structural changes necessary to align with Apache’s principles of meritocracy and sustainability.<\/p>\n


\n <\/p>\n

Graduation to top-level status in October 2025 confirms that Grails now meets Apache’s standards for independent management, a healthy contributor base, and a regular release cadence, following The Apache Way.<\/p>\n

\n<\/p><\/blockquote>\n

James Fredley<\/a>, Apache Grails Project Management Committee Chair and Founder and CEO of Triumph Interactive, describing the release of Grails 7.0, told InfoQ:<\/p>\n

<\/p>\n

Apache Grails 7.0.0, our first stable release following graduation to an Apache Software Foundation Top-Level Project, culminates 18 months of collaborative work and introduces major dependency upgrades and features.<\/p>\n


\n <\/p>\n

This release empowers developers with streamlined full-stack workflows and enhanced security and compliance, and preserves Grails’ foundational DRY and convention-over-configuration principles, all driven by thousands of community commits.<\/p>\n

\n<\/p><\/blockquote>\n

More details on this release may be found in the release notes<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"The release of Apache Grails 7.0.0 delivers bug fixes and notable changes such as: the ability to disable…\n","protected":false},"author":2,"featured_media":167870,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[267],"tags":[1705,365,362,363,364,366,7266,18,117,96370,96368,19,17,18297,96369],"class_list":{"0":"post-167869","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-arts-and-design","8":"tag-architecture-design","9":"tag-arts","10":"tag-arts-and-design","11":"tag-artsanddesign","12":"tag-artsdesign","13":"tag-design","14":"tag-development","15":"tag-eire","16":"tag-entertainment","17":"tag-grails","18":"tag-grails-7-released","19":"tag-ie","20":"tag-ireland","21":"tag-java","22":"tag-micronaut"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@ie\/115508375908337580","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/167869","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/comments?post=167869"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/167869\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media\/167870"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media?parent=167869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/categories?post=167869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/tags?post=167869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}