Sometimes the JAR caching causes significant issues (e.g. JENKINS-20913). It would be great to have a CLI option, which completely disables the caching on the node.
[jar caching] - winp.x64.dll access conflicts
Default jar cache location is hardcoded to ~/.jenkins/cache/jars
Seems like a fix of JENKINS-18578 would solve that kind of issue in a better way. Why not work on that instead of disabling JAR caching altogether?
IMO this could be resolved as duplicate of JENKINS-18578. A safe location should always be available in the slave home path...
Caching sometimes leads to locked files (see JENKINS-20913).
BTW, I don't see failures in newest core version => the priority can be decreased
Closing in favor of JENKINS-18578