Description
When building pkg or dmg on macosx I get file permission 644
When building msi on windows I get file permission 755
When building exe on windows I get file permission 555
The only problem I see with this, is why not have user write permission on exe files ?
This means that without deleting exe in between, you cannot run a jpackage command twice in a row without getting an error the second time, but only for package type exe.
I think we should be consistent, and create all files user writable.
If we want it to be an error that the output file already exists, we should check that ahead of time for all package types, and not rely on failure due to no permission to write file.
When building msi on windows I get file permission 755
When building exe on windows I get file permission 555
The only problem I see with this, is why not have user write permission on exe files ?
This means that without deleting exe in between, you cannot run a jpackage command twice in a row without getting an error the second time, but only for package type exe.
I think we should be consistent, and create all files user writable.
If we want it to be an error that the output file already exists, we should check that ahead of time for all package types, and not rely on failure due to no permission to write file.
Attachments
Issue Links
- duplicates
-
JDK-8266048 regression jpackage built EXE is now ReadOnly
- Closed