PKIX path building failed with custom truststore in Gradle Daemon

When Gradle is configured to use an internal artifact repository with a self‑signed certificate, the build fails with a PKIX path building error even though gradle.internal.http.trustStore and gradle.internal.http.trustStorePassword are set correctly in gradle.properties.

The uncertainty centers on how the Gradle Daemon manages the SSL context lifecycle. If the truststore file is updated on disk while the daemon remains running, it is unclear whether the daemon re‑loads the truststore for each build execution or retains the initial SSL context until the daemon is stopped.

Does the Gradle Daemon refresh the custom truststore on every build execution, or only at startup? Are there any command‑line flags or API calls that force a re‑validation of the certificate chain without manually terminating the daemon process?