Avoid keystore errors by restoring the clean-appdata-on-build behavior

[mgaffigan]

Ant used to clear appdata on build. Without that, the following errors occur when starting the server during development after multiple build-run cycles:

ERROR 2026-07-25 18:02:21.925 [Main Server Thread] com.mirth.connect.server.controllers.DefaultConfigurationController: Could not initialize security settings. java.io.IOException: Keystore was tampered with, or password was incorrect at java.base/com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:882) at java.base/java.security.KeyStore.load(KeyStore.java:1473) at com.mirth.connect.server.controllers.DefaultConfigurationController.initializeSecuritySettings(DefaultConfigurationController.java:1239) at com.mirth.connect.server.Mirth.startup(Mirth.java:221) at com.mirth.connect.server.Mirth.run(Mirth.java:169) Caused by: java.security.UnrecoverableKeyException: Password verification failed ... 5 more

This PR restores the historical behavior.

[github-actions]

Test Results

654 tests  ±0   654 ✅ ±0   3m 25s ⏱️ +43s
108 suites ±0     0 💤 ±0 
108 files   ±0     0 ❌ ±0 

Results for commit 0a8874f. ± Comparison against base commit ac47cc8.

[pacmano1]

Why all of appdata? Why not just the keystore? I might have channels in mirthdb and I am testing stuff and don't want to re-import those channels. I'd make the full appdata wipe opt-in (a flag) and delete just keystore.jks by default.

[mgaffigan]

@pacmano1, I was matching the ant behavior. Something that maintains the DB would be nice if you want to submit something.

[pacmano1]

@pacmano1, I was matching the ant behavior. Something that maintains the DB would be nice if you want to submit something.

so your ask is a flag to "leave mirthdb"?

[mgaffigan]

so your ask is a flag to "leave mirthdb"?

My original goal was to modify Gradle to "copy if newer" for config directory. That would avoid the issue, and preserve the database. I couldn't find a clean way to do that, though.

[tonygermano]

Ant used to clear appdata on build.

Ant ran a clean on build and deleted the entire setup folder, so not exactly original behavior.