Hi everyone, We are facing a strange issue with Grails 4.1.3 that only seems to happen on macOS environments. When running the command below:

grails test-app SomeIntegrationSpec --integration --stacktrace

the compilation fails during

:web:compileGroovy

with several

unable to resolve class

errors for existing domain classes. Stacktrace excerpt:

<=========----> 76% EXECUTING [26s]
> :web:compileGroovy
startup failed:

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/accesstoken/CustomerApiAccessTokenController.groovy: 18: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 18, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/backoffice/AuthorizationTokenAdminController.groovy: 6: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 6, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/backoffice/childaccountconfig/ChildAccountParameterController.groovy: 11: unable to resolve class com.example.domain.criticalaction.CustomerCriticalActionConfig
 @ line 11, column 1.
   import com.example.domain.criticalaction.CustomerCriticalActionConfig
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/checkout/PixAutomaticRecurringCheckoutLimitChangeRequestController.groovy: 8: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 8, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/config/CriticalActionConfigController.groovy: 11: unable to resolve class com.example.domain.criticalaction.CustomerCriticalActionConfig
 @ line 11, column 1.
   import com.example.domain.criticalaction.CustomerCriticalActionConfig
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/customerexternalauthorization/CustomerExternalAuthorizationRequestConfigController.groovy: 8: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 8, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/pix/PixAddressKeyController.groovy: 6: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 6, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/pix/PixAddressKeyController.groovy: 7: unable to resolve class com.example.domain.criticalaction.CustomerCriticalActionConfig
 @ line 7, column 1.
   import com.example.domain.criticalaction.CustomerCriticalActionConfig
   ^

/Users/***/Documents/project/web/grails-app/controllers/com/example/controller/pix/PixAuthorizedDeviceController.groovy: 5: unable to resolve class com.example.domain.criticalaction.CriticalActionGroup
 @ line 5, column 1.
   import com.example.domain.criticalaction.CriticalActionGroup
   ^

> Task :web:compileGroovy FAILED
18 actionable tasks: 1 executed, 17 up-to-date
<-------------> 0% WAITING
> IDLE

ternal.DefaultWorkerServer.execute(DefaultWorkerServer.java:47)
at org.gradle.workers.internal.AbstractClassLoaderWorker$1.create(AbstractClassLoaderWorker.java:46)
at org.gradle.workers.internal.AbstractClassLoaderWorker$1.create(AbstractClassLoaderWorker.java:36)
at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:98)
at org.gradle.workers.internal.AbstractClassLoaderWorker.executeInClassLoader(AbstractClassLoaderWorker.java:36)
at org.gradle.workers.internal.IsolatedClassloaderWorker.execute(IsolatedClassloaderWorker.java:54)
at org.gradle.workers.internal.WorkerDaemonServer.execute(WorkerDaemonServer.java:56)
at org.gradle.process.internal.worker.request.WorkerAction.run(WorkerAction.java:118)
at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:412)
... 3 more

The classes do exist in the project and everything works correctly on Linux environments. Has anyone experienced something similar?

I've seen complex, large gradle projects not find classes due to groovy incremental compile. The only solution was to upgrade groovy or to clean to fix this.

Could it be something to do with the max number of open files that needs to be increased. I know that's the case on Linux.

Hello Team, I recently migrated a multi-module application from Grails 6 to Grails 7.0.1 and am facing a MongoDB lazy-loading issue during GSP rendering. Project structure: • Main Application ◦ Module 1 (contains MongoDB domain classes such as

Test

,

Test1

, etc.) ◦ Module 2 (uses domain classes from Module 1) In a GSP page, I have something like:

test1 class is a Foreign Key(FK) in test class

<g:each in="${testList}" var="test">
    <option value="${test.id}">
        ${test?.test1?.name}
    </option>
</g:each>

After migrating to Grails 7, the page throws the following error:

No datastore session found. Call Datastore.connect(..) before calling Datastore.getCurrentSession()

Interestingly, if I access the association in the controller before rendering the GSP, or if I convert the data to DTOs/maps and pass that to the view, the page works correctly. My questions are: 1. Has datastore session handling during GSP rendering changed in Grails 7 compared to Grails 6? 2. Is there a recommended global solution for this issue instead of manually initializing associations or creating DTOs for every page? 3. Has anyone faced similar issues in multi-module Grails 7 applications using MongoDB references? Any suggestions or best practices would be greatly appreciated.

it sounds like your OSIV config is missing

Stopping Grails app from the command line in Emacs Returning to Grails 7/Java 25 after a couple of years away, I'm developing again. I run Grails from the command line in Ubuntu/Emacs like I've always done, using this alias alias grails="$GRAILS_HOME/bin/grails --non-interactive --plain-output" Starting the app with run-app works as expected. Stopping is another story. If I use Ctrl-C or stop-app surprise! HTML for the the login page is listed. Aside from that, the app looks like it's maybe stopped, but some process keeps running, holding on...

Grails 8 — Data Access with GORM (guide PRs open) Sample: https://github.com/grails-guides/grails-data-access/pull/1 Prose: https://github.com/apache/grails-static-website/pull/517 I’m still learning the guide process — please point out anything I should change on the PRs.

Grails 7: Avoiding legacy Hibernate criteria queries Developing in Grails 7 after a couple of years away. Flooded by warnings about deprecated legacy Hibernate criteria queries. So be it, but I'm working in Grails/GORM, not Hibernate. How does this deprecation reflect to the Grails/GORM level? Do I have to know how GORM is implemented? What kind of GORM queries should I use or avoid, respectively?

Hello. GORM @Service finder fails for a belongsTo association. Is this a bug or intended? I have a domain whose only reference to a related entity is declared through belongsTo

class Entity {
  String name
  static belongsTo = [other: Other]
}

class Other {
   String name
}

And a GORM data service with a derived finder over taht association:

@Service(Entity)
class EntityDataService {
   List<Entity> findAllByOther(Other other)
}

This fails at compile time with:

Cannot implement finder for non-existent property [other] of class [com.demo.Entity]

A dynamic Entity.findAllByOther(other) works fine, so I'd expect t he @Service codegen to resolve it too. I am using Grails 5.2.4

While update Facing issue and not able to identify due to which constrant issue occurring. How to resolve it? The EntityInsertAction was vetoed.. Stacktrace follows: org.springframework.orm.hibernate5.HibernateSystemException: The EntityInsertAction was vetoed.; nested exception is org.hibernate.action.internal.EntityActionVetoException: The EntityInsertAction was vetoed. at org.springframework.orm.hibernate5.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:267) at org.grails.orm.hibernate.GrailsHibernateTemplate.doExecute(GrailsHibernateTemplate.java:305)

Hello, I'm in the process of upgrading from grails 6 to grails 7. We use bootJar to build the jar and it is deployed to our server in a docker container with the cmd java -jar. In grails 6 the application started up with the production as the active profile, but now it is starting up with development as the active profile. We haven't made any changes to our process so this seems odd. Is there something that changed that would cause this?

How do you generally manage upgrading the versions of things you specify in

gradle.properties

in your projects? I enabled dependabot for gradle but it apparently does not manage

gradle.properties

correctly. I hacked a GitHub workflow to check Maven central for new version of Grails and make a decision based on curl/grep/tr output. I would like to have something working for other version I've specified in

gradle.properties

, do you know if there is something? My AI is suggesting to move from `gradle.properties`to

libs.versions.toml

but I'm unsure this is a good option.

@User you may be interested in this ^^

hmans.dev/blog/chatto-is-open-source I saw this on the HN, could we use this replace slack?

Hi team, could you please give your best estimate when you expect Grails 8 will be officially released? I'm considering upgrade paths for a client and would like to give a ballpark quarter/year.

How to use micronaut declarative client into grails 7.2.0 I have prepared a configuration for use Micronaut Declarative client into grails 7.2.0 I got an error: Error creating bean with name 'example.grails.IndexController': Error creating bean with name 'mainService': Unsatisfied dependency expressed through field 'client': No qualifying bean of type 'example.grails.MainClient' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Autowired(required=true)}...

Hello, we are fixing failing integration tests as part of an upgrade from grails 6 to 7. We're seeing an issue where when instantiating a domain class using a named parameters constructor, the field values are not being set. Has anyone else experienced this or have any idea why this may be happening? Or have any suggestions for troubleshooting this issue?

Hi everyone! We’re looking into how to do test impact analysis for a large Grails 4 monolith (Groovy, Gradle, Spock integration tests with Testcontainers). The goal is to make our CI smarter by running only the specs actually affected by a given diff, instead of executing the entire test suite on every PR, which is getting increasingly slow and expensive as the codebase grows. Has anyone tackled a similar challenge (Grails/Groovy or any large monolith)? What approach worked for you to reliably map code changes → impacted tests?

Grails 7.2.2 package/assemble fails with Snakeyaml "LoaderOptions must be provided" Developing with Grails 7.2.2/PostgreSQL 17 on Ubuntu 24.04.4 LTS worked well (although I've been away from Grails for a couple of major versions). Then came the final step, deployment the new way. gradle assemble ...

Task :compileGroovyPages FAILED

Exception in thread "main" java.lang.NullPointerException: LoaderOptions must be provided. at org.yaml.snakeyaml.constructor.BaseConstructor.(BaseConstructor.java:120) This leaves me completely stumped. I do use traditional GSP views (that...

Hi team, We are getting ready to roll out the upgrade for our app from Grails 5 to Grails 7.2.2. We are doing pretty extensive load testing, and I am going through the Grails release notes, but is there anything specific that I should be aware of to ensure a smooth upgrade?

Hi everyone, I’m not sure if this will be useful to anyone else, but I put together a small Grails example application showing how to integrate Grails with Keycloak. I created it while working through Keycloak authentication for an application I’m currently building, and I documented the setup along the way, including PostgreSQL, client roles, authorization, and email configuration. The example is here: github.com/amondel2/grails-keycloak-example If this is something that would be useful to the Grails community, I’d be interested in any feedback. Also, if there is a better place for something like this, please let me know.

Looks good! Thanks! You should really consider creating a Grails Guide (grails.apache.org/guides)

Hello here testing Grails 8.0.0-M5 with spring security core and database migration plugins, and devtools configured. On Bootstrap phase, the applications fails to start, raising this error: java.lang.IllegalArgumentException: Not an entity: class com.example.Role Running Claude Code AI, it determined this: The IllegalArgumentException: Not an entity: class com.example.Role wasn't a problem in your Role.groovy/User.groovy/BootStrap.groovy — those are all correctly written. It's a compatibility bug between Spring Boot DevTools' restart classloader and GORM/Hibernate5 on this exact stack: Grails 8.0.0-M5 + Hibernate ORM 5.6.15 + Spring Boot 4.1.0. How I confirmed it: - Reproduced the crash reliably via bootRun against your dev MySQL. - Proved it wasn't Role-specific — swapping in User.count() first hit the identical "Not an entity" error, and it also failed from a live HTTP request long after startup completed, ruling out a boot-order race. - Isolated it to Criteria-based GORM calls specifically: Role.count()/Role.list() failed, but Role.get() and raw HQL worked — and .save() threw a field/getter reflection IllegalArgumentException, the textbook signature of the same class name being loaded by two different ClassLoaders. - Removing spring-boot-devtools from the classpath made count(), list(), and save() all work immediately (thread name also switched from restartedMain to plain main, confirming DevTools' restart classloader was the split). - Re-verified end-to-end with a clean DB: BootStrap now logs Generated admin credentials: admin / <uuid> with zero errors. What I changed: - build.gradle — commented out developmentOnly "org.springframework.boot:spring-boot-devtools" with an explanatory comment. - Everything else (BootStrap, application.groovy, domain classes) is back to exactly how you had it — my diagnostic edits (temp DiagController, debug logging, a scoped /diag security rule) were all reverted. - Cleaned up the one leftover test row I'd accidentally committed to the role table during diagnosis. Tradeoff: you lose DevTools' auto-restart/LiveReload during development until this Grails milestone/Hibernate5 combo is fixed upstream (worth watching Grails' issue tracker, since 8.0.0-M5 + Spring Boot 4 is very fresh). If LiveReload matters a lot to you, let me know — there may be workarounds worth exploring (e.g., excluding grails-app domain classes from DevTools' restart classpath), but I'd want to test that carefully rather than guess.

Not a question, but wanted to flag as this just actively burned us. Hopefully this helps others avoid the hard lesson! StringBuilder saves the day again 😅

Grails PageRenderer dysfunction in deployed war With Grails 7.2.2 I'm using grails.gsp.PageRenderer in a controller to generate static HTML pages, as follows. The PageRenderer is injected into the controller the usual way. def page = groovyPageRenderer.render view: '/event/showStored', model: model Works fine in development, but when running from a deployed war java -jar app-version.war pages are generated, but their size is zero. There is no exception or anything. Any pointers or clarification?

Is it planned to certificate Grails for Compliance ISO 27001?

Hi. Is there a "Micronaut-community" in Slack?

Should I really ask migration questions (Grails 5 => Grails 7) " on lists.apache.org/list.html?… and paste the link here" as suggested in this channel's Topic? That list seems very quiet, and more focused on the development of Grails (thanks, you wonderful people!), not my basic/beginner questions #C6NJV8RCG seems like the right place to ask migration questions, which I tried without success, quite possibly because no one wants to spend time dealing with that stuff 😆 Anyone have a better suggestion for where I can find help migrating -- ideally, a community of other people who've already gone through the pains of migration and documented some of the fixes/issues/etc they ran into?

@Tracy Logan I don't think many people are aware of #C6NJV8RCG so asking here is probably better. The

<mailto:user@grails.apache.org|user@grails.apache.org>

is for user questions, where as

<mailto:dev@grails.apache.org|dev@grails.apache.org>

is focused on Grails development. If you post your

<mailto:user@grails.apache.org|user@grails.apache.org>

you actually help promoting that list and migrating the questions of Slack

Hi — is there a milestone release planned for grails-web-console 8.0.x? I’m running Grails 8.0.0-M6, and console 7.1.0 fails on

/console

because it uses the removed Metadata accessor (

app.grails.version

). I noticed the fix is already on 8.0.x and #27 mentions releasing a milestone. Is anything blocking that, or is there a published snapshot we can try? Happy to test it against our application.