James Fredley

3 more are passing https://github.com/grails/grails-functional-tests/pull/251 13 left

I can confirm that with `developmentOnly("org.springframework.boot:spring-boot-devtools")` this error occurs on a Grails 6.2.0 project and without it does not occur.

https://github.com/grails/grails-core/blob/c0ac9667e5d55db544cd62155ad17f8322ca1b25/grails-console/src/main/groovy/grails/ui/command/GrailsApplicationContextCommandRunner.groovy#L43-L59 https://github.com/grails/grails-core/blob/c0ac9667e5d55db544cd62155ad17f8322ca1b25/grails-core/src/main/groovy/grails/boot/GrailsApp.groovy#L97-L113

Latest conversation: https://github.com/orgs/grails/discussions/13517#discussioncomment-10453329

@codeconsole @matrei Do you know how to convert `installToHomeDist` from an `Upload` task to a `maven-publish` task?

This was consolidated down to the following. The build was no longer using `flatDir name: 'libs'`, so it was removed. ``` tasks.withType(PublishToMavenLocal).configureEach { doLast { ant.copy(todir: homeDistDir, flatten: true, includeEmptyDirs:...

It has been removed for the upcoming Grails 7 release. For prior versions, this is an intermittent issue that might be caused by a 400 error on the spring repo...

@kephakhang I would take a look at the Grails 6.2.1 release which removes http-builder entirely and make sure you are running Gradle 7.6.4 for Grails 6. Grails 7 will be...

@davydotcom I wasn't around for that historical context, but it would be great to keep config key access via dot notation and get rid of these warnings.

related to: https://github.com/grails/grails-core/issues/10188 https://github.com/grails/grails-core/pull/10280