Not a showstopper, more a curiosity, as it doesn't...
# questionsj
John Moore
07/24/2025, 3:58 PMNot a showstopper, more a curiosity, as it doesn't appear to cause any problems, but...
At some point in attempting to build or run a Grails 7 app, converted from Grails 6, a new directory has been created called 'USER_HOME_IS_UNDEFINED'. It contains a '.grails' directory.
g
giangio
07/24/2025, 4:05 PMI dont' know if it's the same but I had this issue, it is probably still to be fixed: https://github.com/apache/grails-core/issues/12874
giangio
07/24/2025, 4:07 PMI've replied too quickly, I guess that's not the problem
j
James Fredley
07/24/2025, 4:09 PMIs this after running ./grails or ./grailsw?
j
John Moore
07/24/2025, 4:28 PMIt's a Grails 7 thing, even if it originates in my app, as it has not occurred befor,e in 5 or 6. Not sure what precipitated it, it was a while before I noticed the directory.
j
James Fredley
07/24/2025, 4:29 PMDoes it have a wrapper directory under .grails?
James Fredley
07/24/2025, 4:29 PMNormal that lands in
~/.grails/wrapper
James Fredley
07/24/2025, 4:31 PMIntelliJ (I'm guessing the Grails plugin) also stores some print settings is ~/.grails/scripts
j
John Moore
07/24/2025, 4:32 PMNo, the .grails directory contains a directory called spring.application.name_IS_UNDEFINED, in which there is a stacktrace.log.
j
James Fredley
07/24/2025, 4:51 PMSee if groovy can find
user.home Copy code
println System.getProperty("user.home")j
John Moore
07/24/2025, 5:00 PMDeleted the 'USER_HOME_IS_UNDEFINED' directory, did ./gradlew bootRun, and my user home directory was correctly printed out - but the rogue directory was recreated.
j
James Fredley
07/24/2025, 5:27 PMI am at a loss. AI's suggest was to check logback-spring.xml or if you still have it named logback.xml rename to logback-spring.xml and check it against the one generated from start.grails.org
James Fredley
07/24/2025, 5:27 PMI have not see this personally and have run hundreds of Grails 7 apps over the last year and I think you may the first to report it.
j
John Moore
07/24/2025, 5:30 PMI wouldn't worry about it. As I said, it was not a showstopper and doesn't cause any problems, it was just a bit of an oddity.
John Moore
07/24/2025, 5:38 PMThanks for looking, though!
John Moore
07/24/2025, 5:49 PMI do have a logback-spring.xml, converted (by AI) from logback.groovy which I had before. Looks OK to me:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<conversionRule conversionWord="clr" converterClass="org.springframework.boot.logging.logback.ColorConverter" />
<conversionRule conversionWord="wex" converterClass="org.springframework.boot.logging.logback.WhitespaceThrowableProxyConverter" />
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<charset>UTF-8</charset>
<pattern>
%clr(%d{yyyy-MM-dd HHmmss.SSS}){faint} %clr(%5p) %clr(---){faint} %clr([%15.15t]){faint} %clr(%-40.40logger{39}){cyan} %clr(:){faint} %m%n%wex
</pattern>
</encoder>
</appender>
<springProfile name="development">
<property name="LOG_FILE_LOCATION" value="${USER_HOME}/.grails/${spring.application.name}/stacktrace.log" />
<appender name="FULL_STACKTRACE" class="ch.qos.logback.core.FileAppender">
<file>${LOG_FILE_LOCATION}</file>
<append>true</append>
<encoder>
<charset>UTF-8</charset>
<pattern>%level %logger - %msg%n</pattern>
</encoder>
</appender>
<logger name="StackTrace" level="ERROR" additivity="false">
<appender-ref ref="FULL_STACKTRACE" />
</logger>
</springProfile>
<root level="ERROR">
<appender-ref ref="STDOUT" />
</root>
<logger name="grails.app" level="INFO" additivity="false">
<appender-ref ref="STDOUT" />
</logger>
<logger name="org.hibernate.orm.deprecation" level="ERROR" additivity="false">
<appender-ref ref="STDOUT" />
</logger>
<logger name="org.springframework.web.socket.config.WebSocketMessageBrokerStats" level="ERROR" additivity="false">
<appender-ref ref="STDOUT" />
</logger>
<logger name="org.grails.config.NavigableMap" level="ERROR" additivity="false">
<appender-ref ref="STDOUT" />
</logger>
</configuration>