A blog-post about all the goodies in Grails 8 is pending review, and will be published very soon!

how to Handle the Date API grails legacy to grails 6 migration 1. Binding: configure dateFormats Grails binds dates only with the formats it knows. If your forms send dd/MM/yyyy, list it explicitly (this replaces the defaults, so re-add any ISO format you need): grails: databinding: dateFormats: - 'dd/MM/yyyy' - 'dd/MM/yyyy HH:mm' - 'yyyy-MM-dd' - "yyyy-MM-dd'T'HHmmss.SSSX" convertEmptyStringsToNull: true For one odd field use @BindingFormat('dd/MM/yyyy') on a command-object property. params.date('x', 'dd/MM/yyyy')...

This Grails 8 release is amazing! I don't remember a release which felt so important since Grails 2 was released. Thank you Grails team!

is the Criteria library retired in Grails 8? (we use it heavily/exclusively almost)

Grails asdf plugin is working again! We just tried here. Some months ago I talked to Weibe Moura, the author of the Grails asdf plugin about the problems it had downloading and using Grails. If you dont know asdf, here is the website: asdf-vm.com Just tried here again, and it's working. This is great news for everyone which uses asdf as the main tool as runtime version manager instead of sdk (asdf deals with other ecosystems beyond the JVM (I use it a lot for Node, Go, Rust, Java, PHP and many, many other things. To use is really simple: asdf plugin add grails Than asdf install grails [version] - asdf install grails 8.0.0 asdf set grails [version] - asdf set grails 8.0.0 And it's done.

The Grails asdf plugin repository - github.com/weibemoura/asdf-grails.git

A common questioning I'm receiving when telling people about the new edition of my book (about Groovy and Grails): "what is the relevance of Groovy and Grails on this new AI world?" I think this is a hard question: why would anyone choose Groovy and Grails instead of Spring Boot on this new reality? In a world in which you have techniques like Spec Driven Development (could we call this "cascade 2.0"? 🙂 ) where we can rewrite a system in other languages and frameworks, how to compete? How to answer these questions?

Hi folks, this was working in Grails 6, it's not working anymore in Grails 8 , i get this exception: java.lang.IllegalArgumentException: Invalid sort property Sort:

fetchParams.sort = [
    'date'               : 'asc',
    'individual.lastname': 'asc',      // <- This is not working anymore
]

used in:

List<TWorkLog> listAll(Map filterParams = [:], Map fetchParams = [:]) {
    if (!fetchParams.sort) fetchParams.sort = [dateTimeStart: 'asc']
    if (!fetchParams.fetch) fetchParams.fetch = fetch

    def query = buildQuery(filterParams)
    return query.list(fetchParams)
}

With a where query:

@CompileDynamic
private DetachedCriteria<TWorkLog> buildQuery(Map filterParams) {
    def query = TWorkLog.where {}

    ...

    return query
}

Reading the documentation I am supposed to create an alias for the association, something like

def sortIndividual = individual

and then sorting on that. Since we have an automation in table headers that automatically sort columns based on their names, I was wondering if there is a way to revert to the old behaviour

BTW: The old way was much more intuitive for an end user

Like sorting is something basic that should not require "workarounds"

Okay, I don't want to sound alarming, but we have built a whole system on that feature. At the moment we are unable to sort recordsets by column properties. The following is not working on Grails 8, adding the alias to the where query:

def query = TWorkLog.where {
    def individualSort = individual
}

// Adding other fragments to the query...

Then sorting with the following:

fetchParams.sort = [
    'date'                   : 'asc',
    'individualSort.lastname': 'asc',      // <- This is not working anymore
]

throws:

java.lang.IllegalArgumentException: Invalid sort property

ATTENTION PLEASE Forget about that issue. It works. And I need rest.

“What issue?”

In the end I have an issue (apart from the evident personal one) with where queries and sort, but I'll take my time to write it down properly

assetCompile fails for me on a freshly forged grails 8 app with the OpenAPI/Swagger UI feature enabled. Is this known?

I know there is talk on the dev mailing list about Hibernate 7+ vs H5.6 in upcoming Grails releases. To provide some anecdotal info: we’re in the process finishing a migration of an app of significant size and complexity to Grails 8 using Hibernate 7.4. There are definitely bugs (some reported, more reports on the way, and thank you to the people who have fixed some already!), but nothing we have not been able to work around so far (and we use Criteria pretty heavily).

My view is the Grails 10 should be the first time H5.6 deprecation can be discussed. 8 and 9 are dual hibernate. I have several apps on h7.4, and have been happy so far. It was a massive lift and is the future. That said, we want it to be an orderly transition and h5.6 is far more tested and trusted today.

I am trying to move to Hibernate7, I have many issues with the tenants but basically it's the

Not an entity:

exception. I have methods annotated with @CurrentTenant that must acccess the default tenant. So I have a nested @WithoutTenant. Neither me nor the AI have found a solution yet. The code works with H5. How can I tell GORM to query the default tenant when I am in the context of a current tenant? Or is that a bad practice? We have User/Groups/Tenants/Connections/AuthenticationProviders domain objects only on the default tenant, they serve all the tenants.

That's the other exception I get:

TenantException: Cannot resolve a single current tenant: [test, default] are bound on this thread for different datastores. Use get(Datastore) to select the tenant of the datastore being operated on.

there have been numerous fixes to the tenant code, have you tried the latest snapshot build?

Nope, I am not in a hurry, I'll wait the 9.0 release 🙂

Is anyone else experiencing troubles with repo.grails.org ? Our CI is constantly getting errors downloading jars from there

could also be related to a jdk update (community.boomi.com/…/openjdk-java-11-0-30-may-cause-tls-ssl-handshake-failure-exception-due-to?sysparm_article=KB0015435&… )

I would suggest you use maven central

I should mention this is an old grails version (4.x)

Could not find org.grails:grails-datastore-gorm-support:7.0.8.RELEASE.

so i need the grails repos (or some mirror)

ah, yeah, Jfrog provides that to us, but it seems to be flaky at times - we see over 48TB a month downloaded from it

hence, we've been slowly suggesting people move to maven central

I'd like to contribute to the Grails project. To get started, I'm scanning for CVEs on Grails (I just opened an issue github.com/apache/grails-core/issues/16789) and applying some patches to the problems I can find (basically replacing problematic libraries first) How do I get started?

Is anyone else hitting issues with rate-limiting on various Github actions that invoke Grails jars? We have backend Spock unit tests that need to download a Grails jar to run each time, and we’re getting 429's very often in this process, which kills the unit tests and causes Github to report a failure. I think this might be related to the issue @pieter mentioned above?