Dear all, the IntelliJ Grails Plugin has on my machine problems. I installed an own build from apache-grails-intellij-plugin-262.0.1 and everything worked like charm. After upgrading the plugin to its release version, the plugin doesn't work any longer. Even after reinstalling my own build, it doesn't work any longer. Can someone provide help? Or point me to the direction where I can analyse teh problem on my own? The plugin is one of the thinhs I would like to contribute most. Thanks in advance, Reto

Same with latest Snapshot Build

I cannot help, but I can tell you, that it works here. There is a list of required modules that needs to be enabled, perhaps one of those are missing?

@retokiefer can you take a look at your logs and see if there is an error?

Thanks to you both. I think I have all dependencies installed. In the Logfile there is no error. Neither while deinstalling and reinstalling the plugin nor during grails project opening. The Grails new project wizard works, but no Grails View, Action buttons for Controller, Views etc. And GSP support seems to be missing as well.

it must not be detecting your project; is it a multiproject build?

also, it only takes effect when gradle syncs - is the gradle sync working?

No it is a single project build. I'll check the gradle sync - thanks for your suggestions!

One addition, that is propably related to the plugin: If I create a run Configurations i got the error: Run Configuration Error: Grails application is not selected Maybe the project I am working on is broken...?

I even uninstalled IntelliJ and deleted the plugin folder - same as before.

if you use the gradle project window and click refresh, does it sync hte project?

Thanks @jdaugherty that hint was very helpful: Summary • Gradle sync failed because the Grails IntelliJ plugin calls implementation.copy(Spec), which Gradle 9 rejects on a declarable configuration. • implementation is now replaced by a resolvable configuration of the same name before that plugin hook runs. Changes • In build.gradle, the original implementation object stays on the compile/runtime classpaths. • Name lookup returns a resolvable copy, so the IDE plugin can copy and resolve it. It is running again - thanks indeed! 🙂 I really would like to contribute to the plugin. If you have documentation or sometime halve an hour free time, I really would like to start with working on the IntelliJ plugin. Best, Reto

Not a question--just a heartfelt thank you to the Grails team for the 8.0.0 release! This is a huge and important milestone, and we really appreciate all the work that went into it.

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.