fix(spring): Resolve archetype working dir from user.dir when PWD is unusable

The post-generate script took the shell working directory from the PWD
environment variable to resolve a relative -DprojectDirectory. Under Git Bash on
Windows, PWD is a Unix-style path (e.g. /c/Users/...) that java.io.File
mis-resolves to a bogus drive-relative path, so the generated tests were copied
outside the project and a stray demo project (its pom.xml included) could be left
behind. Trust PWD only when it names an existing directory on this platform;
otherwise fall back to user.dir, the real JVM working directory.

Also correct the README and archetype docs to use a cross-platform relative
scratch directory (target/audit-scratch) instead of a Unix /tmp path that is
mis-resolved on Windows.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UkRk16pW4VEM3E6vrDoG5y

Author: jeffjensen

README.adoc

@@ -20,7 +20,7 @@ mvn archetype:generate -DinteractiveMode=false \
   -DartifactId=demo-audit-tests \
   -Dpackage=com.example.demo \
   -DschemaPropertyName=database.datasource.schema-name \
-  -DoutputDirectory=/tmp/audit-scratch \
+  -DoutputDirectory=target/audit-scratch \
   -DprojectDirectory=.
 ----
 

archetype/src/main/resources/META-INF/archetype-post-generate.groovy

@@ -13,12 +13,14 @@ if (!targetDirProp) {
     targetDirProp = System.getProperty('projectDirectory')
 }
 
-// A relative projectDirectory resolves against the shell's working directory. Prefer the PWD
-// environment variable: the shell exports it and, unlike user.dir, it cannot be mutated by a
-// System.setProperty call inside the running JVM. Fall back to user.dir when PWD is absent (e.g. on
-// Windows). Tests inject _pwd through the Groovy Binding to stand in for PWD.
-def pwdOverride = binding.hasVariable('_pwd') ? (String) binding.getVariable('_pwd') : null
-def workingDir = pwdOverride ?: System.getenv('PWD') ?: System.getProperty('user.dir')
+// A relative projectDirectory resolves against the shell's working directory, taken from the PWD
+// environment variable (the shell exports it and, unlike user.dir, it cannot be mutated by a
+// System.setProperty call inside the running JVM; tests inject _pwd through the Groovy Binding to
+// stand in for it). Under Git Bash on Windows, though, PWD is a Unix-style path (e.g. /c/Users/...)
+// that java.io.File resolves to a bogus drive-relative path, so trust PWD only when it names an
+// existing directory on this platform; otherwise fall back to user.dir (the real JVM working dir).
+def pwd = binding.hasVariable('_pwd') ? (String) binding.getVariable('_pwd') : System.getenv('PWD')
+def workingDir = (pwd && new File(pwd).isDirectory()) ? pwd : System.getProperty('user.dir')
 
 def resolveDestRoot = { prop ->
     if (!prop) {

integration/src/site/asciidoc/archetype.adoc

@@ -53,7 +53,7 @@ mvn archetype:generate -DinteractiveMode=false \
 
 == Generate tests only (for an existing project)
 
-*Point `-DoutputDirectory` at a pom-less scratch directory* (e.g. `/tmp/audit-scratch`) — the plugin refuses
+*Point `-DoutputDirectory` at a pom-less scratch directory* (e.g. `target/audit-scratch`; use a path valid on your OS — a Unix-style `/tmp` path is mis-resolved on Windows) — the plugin refuses
 to generate into a directory containing a `pom.xml`, and when run from inside a Maven project it tries to add
 the result as a `<module>`. The scratch location avoids both pitfalls; only the post-generate copy step writes
 to your project.
@@ -86,7 +86,7 @@ mvn archetype:generate -DinteractiveMode=false \
   -DpostgresImage=postgres:16 \
   -DdisabledTests=false \
   -DdataSourceNames=none \
-  -DoutputDirectory=/tmp/audit-scratch \
+  -DoutputDirectory=target/audit-scratch \
   -DprojectDirectory=.
 ----