OpenAPITools / OpenAPITools/openapi-generator
[BUG] the generated gradlew file does not have the correct permission
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
The gradlew file in the generated project (like in samples/) is wrong.
If you run .gradlew build in samples/client/petstore/java/okhttp-gson you get:
-bash: ./gradlew: Permission denied
Workaround: run chmod +x gradlew before starting gradle.
I think gradlew is a supporting file. We probably need something like this after generation.
private void setExecutable(Path file) throws IOException {
Set<PosixFilePermission> perms = new HashSet<PosixFilePermission>();
//add owners permission
perms.add(PosixFilePermission.OWNER_READ);
perms.add(PosixFilePermission.OWNER_WRITE);
perms.add(PosixFilePermission.OWNER_EXECUTE);
//add group permissions
perms.add(PosixFilePermission.GROUP_READ);
//add others permissions
perms.add(PosixFilePermission.OTHERS_READ);
Files.setPosixFilePermissions(Paths.get(file).getAbsolutePath()), perms);
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with samples/client/petstore/java/okhttp-gson and inspect how the generated gradlew file is created and copied into that project. Confirm the executable permission is preserved or set during generation, then rerun ./gradlew build without the chmod workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100