James Fredley

@codeconsole Please verify that grailsw now has the correct line endings on https://github.com/grails/grails-wrapper/releases/tag/v5.0.0

It was copied from a Windows machine and my guess is that the line endings were changes during `git clone`. Those files have not changed since 2017: https://github.com/grails/grails-wrapper/tree/5.0.x/shell

@codeconsole Did you have `mavenCentral()` in `repositories{}` and `profile ("org.grails.profiles:web")` in `dependencies{}` when the error occurred? If you run `gradle assemble` do you get the same error? `Error Could not...

@codeconsole the `Error Could not resolve all artifacts for configuration ':testRuntimeClasspath'. Type 'gradle dependencies' for more information` issue can be resolved with the following. `grails-wrapper` can only load on a...

https://github.com/grails/grails-core/pull/13648 - a WIP for duplicatesStrategy at a higher level

I do not know why, but with Gradle 8 this is occurring more often.

For the org.grails.spring.context.support.PluginAwareResourceBundleMessageSource related errors, StaticMessageSource is the expected MessageSource type for testing which provides an addMessage method. The bean is set as StaticMessageSource here: https://github.com/grails/grails-testing-support/blob/4.0.x/grails-testing-support/src/main/groovy/org/grails/testing/GrailsApplicationBuilder.groovy#L170-L189 `messageSource(StaticMessageSource)`

https://github.com/grails/grails-testing-support/pull/431 fixes 28 of the ~52 new failing tests.

That made an massive difference. Down to 3 distinct test failures on https://github.com/grails/grails-core/pull/13702/files, these each get run 3 times on https://github.com/grails/grails-core/actions/runs/11079311377/job/30823450376

The remaining 3 new failing tests: https://github.com/grails/grails-core/pull/13702/files#diff-6889bb937b05f118cd7a9dc1f21e76edb66bbd53ea8901923d90c284f7f2c4b5 https://github.com/grails/grails-core/pull/13702/files#diff-d7674e06b1294ce8a4fae2ab1606c48dbd1ff7c1eddb037dfd868dcc59f8fa7e