i18n: say only what was observed about the leaked JVM default locale

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Uu7q8vPeREyT4218EJPzz1
This commit is contained in:
Claude
2026-09-24 10:01:36 +00:00
parent 2cbf31e7d5
commit a2cc7bbd08
2 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -29,7 +29,7 @@ mvn test # runs every scenario and rewrites output/01-11
The tests pin the JVM to `-Duser.language=en -Duser.country=US -Dfile.encoding=UTF-8` (see `pom.xml`) so the
transcripts do not depend on the machine they were generated on, and run each test class in its own JVM
(`reuseForks=false`) because Tomcat reads the JVM's default locale once.
(`reuseForks=false`) because a test that changes the JVM's default locale once leaked it into another test's transcript.
## Profiles
@@ -7,8 +7,8 @@ import java.util.Locale;
import static org.assertj.core.api.Assertions.assertThat;
/**
* Transcript 02. Changes the JVM's default locale, and Tomcat reads that default once per JVM, so this class runs in its own
* JVM (surefire reuseForks=false) and cannot leak a Hindi default into the "no Accept-Language header" row of transcript 01.
* Transcript 02. Changes the JVM's default locale. In an earlier run a Hindi default set here leaked into the
* "no Accept-Language header" row of transcript 01, so this class runs in its own JVM (surefire reuseForks=false).
*/
class SystemLocaleFallbackTests {