Closed fmasa closed 5 months ago
I have seen this behavior on mac, I didn't realise its was due to the permissions, do you know of a solution?
AFAIK the Gradle Copy
task supports change of file permissions, so leveraging that to add the write permission for the jars should do the trick. I'll take a look at it in a few days. You can assign this issue to me, so I don't forget 😅
When
copyAars
is executed, the some jars copied tobuild/jar
do not have write permissions on them. When this task is executed again, it fails because it now tries to overwrite file that is read only.This means that when working on this library I have to run
clean
task between every build. This happens on Linux (and I would expect this to be the case on Mac as well).Failed tasks correspond to the files without write permissions:
This is the result of
ls -lh build/jar
: