-
Notifications
You must be signed in to change notification settings - Fork 148
Description
Hello!
I'm submitting a…
- bug report
- feature request
- other
Short description of the issue/suggestion:
In the packageMyAppForLinux task I have added a file into additionalResources to be included in the package. The original file is marked as executable (chmod +x) but when packaged into the tarball it does not keep that permission.
Can you please help me to solve this issue?
What is the expected behavior?
I am expecting the packaged file to keep the permissions of its original file. (In my case the executable permission)
What is the current behavior?
It does not keep the original file permissions. (In my case the executable permission)
Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?
Here is my packageMyAppForLinux task:
The file blue-cube.desktop is the one I want to preserve its permission when packaging.
task packageMyAppForLinux(type: io.github.fvarrui.javapackager.gradle.PackageTask, dependsOn: build) {
platform = io.github.fvarrui.javapackager.model.Platform.linux
createTarball = true
outputDirectory = file("$buildDir/bundles/linux-x64")
additionalResources = javapackager.additionalResources + [file('blue-cube.desktop')]
}
Please tell us about your environment:
- JavaPackager version: 1.6.3
- OS version: Linux Mint 20.1 Ulyssa
- JDK version: 14
- Build tool:
- Maven
- Gradle
Regards