Spring camunda.bpm.deployment-resource-pattern property issues

I configured my engine with the following configuration:

camunda.bpm.deployment-resource-pattern: file:///resources/deployment/**/*.*

When the files are found in the Windows environment (after a lot of suffering configuring a path that can be used in Windows), the deployment defines the “full path” of the file… so when my JavaScript is deployed, I have to somehow configure the Script Task to point to an External Rescource something like:

"deployment://C:/Users/deploymentuser/somepath/script.js"

Is there an out of the box way of doing this better? Why this does not seem to happen in Camunda Run “custom” deployment directory? Are there Java casses ready to do that correctly?
This is for an enterprise client… is there something ready for this?
Shouldn’t something like the Java user.dir be removed from the “front” of the filename or something like that?