hotreload & multi-project: doFindPathMatchingFileResources looks after resources into the wrong path

[Taack]

Expected Behavior

Translations should work as for a regular bootRun

Actual Behaviour

Either launching ./gradlew server:bootRun -Dgrails.run.active=true or adding in server/build.gradle:

bootRun {
    doFirst {
        classpath = classpath.filter { file ->
            boolean r = true
            gradle.ext.taackPlugins.each { p ->
                r = r && !file.path.contains(p + '-' + version + '.jar')  // Exclude the JAR to avoid duplicates
            }
            r
        }
        gradle.ext.taackPlugins.each { p ->
            classpath = classpath + project(':' + p).sourceSets.main.output  // Add classes and resources output
        }
    }
// [. . .]

Seems to results in message.property files not being included.

Steps To Reproduce

First we import the infra into local maven:

1. clone the infra repo: git clone git@github.com:Taack/infra.git
2. into this repo, ./gradlew publishMavenPublicationToMavenLocal

Then

1. clone the intranet repo: git clone git@github.com:Taack/intranet.git
2. swith to branch g7s2: git switch g7s2
3. Launch with ./gradlew server:bootRun -Dgrails.run.active=true (i18n NOK, hotreload OK), ./gradlew server:bootRun (i18n OK, hotreload NOK)...

Environment Information

• Linux cachyos-x8664 6.17.1-2-cachyos Grails fails to correctly identify Java Home in startGrails #1 SMP PREEMPT_DYNAMIC Mon, 06 Oct 2025 15:17:14 +0000 x86_64 GNU/Linux
• java full version "24.0.2+11-jvmci-b01"

Example Application

No response

Version

Grails 7.0.0-RC2

[Taack]

Just fixed the test case build (using Grails 7.0.0-RC2) and also put the propoer bootRun commands in the previous message...

The login / password is admin / ChangeIt (see in server/grails-app/conf/application.yml)

Thanks for your support

[Taack]

After trying in a clean env, I cannot reproduce using ./gradlew server:bootRun -Dgrails.run.active=true, hotrestart is not working. So I pushed the version with the closure in bootRun (see server/guild.gradle), here i18n is broken but hot reload is working.

[Taack]

After digging a little, it turns out that org.grails.plugins.BinaryGrailsPlugin#getProperties does not list resources if baseResourcesResource (the classpath entry) point to a non-jar directory.

            try {
                // first load all properties
                Resource[] resources = resolver.getResources('*' + PROPERTIES_EXTENSION);
                resources = resources.length > 0 ? filterResources(resources, locale) : resources;
                if (resources.length > 0) {

resources.length is zero because resolver.getResources return an empty array.

It seems doFindPathMatchingFileResources look after the wrong path: .../build/resources instead of .../build/resources/main where the properties are stored.

[Taack]

FYI, Resource resource = baseResource.createRelative(location); in org.grails.core.io.StaticResourceLoader:51 seems to shrink the resource path. I prefer to not modify anything here.

Regards

[Taack]

I just updated the test-case for Grails 7, modifications include:

• cleaned up buildSrc;
• use for loops instead of each with closure;
• Use Grails 7.0.0 instead of Grails 7.0.0 RC2.

If you modify app/crew/grails-app/controllers/CrewController, the app is Hot-restarted, but i18n is broken.

If you apply the patch provided by the pull request, i18n is OK.

It runs perfectly with Java 24 (OpenJDK)

Regards

[Taack]

Following today's meeting, I could reproduce the issue with a simple test-case. The gradle files are based on the ones generated by Grails forge.

test-i18n-multiproject2.tar.gz

Steps:

> cd test-i18n-multiproject2/server
> ../gradlew bootRun

In another terminal

> curl http://localhost:8080/test
test.label
> curl http://localhost:8080/test?lang=fr
test.label

test.label is a key, not the translation.

Hot restart is working properly, but i18n is broken. The patch provided by the PR fixes i18n.

test.label is translated in the app/test plugin.

Note: it does not work when using ./gradlew server:bootRun, you have to execute gradle from the server directory.

Hope this helps !!

[Taack]

Here is the buildSrc version using exploded plugin. Logging is working correctly after a hot restart. This test-case is much cleaner than previous ones.

test-i18n-multiproject-buildSrc.tar.gz

To summarize:

• the app folder holds grails plugins, here, only test plugin is added;
• the server folder is the main app;
• we use buildSrc semantic to simplify all build.gradle into plugins and main app;
• i18n is defined into plugins;
• we have to launch bootRun task from server directory.

In our use-cases, bootRun completely breaks the UI, because we try to find the right translation automatically iterating over many keys (from more specific to generalized ones, like offer.salesman.usernaname.label, then salesman.usernaname.label, then user.usernaname.label, then default.usernaname.label).