Inconsistent file permissions in generated Quarkus Maven project.

[xorye]

When generating a Maven project by calling 'Quarkus: Generate a Maven project' in the command palette, the final project that is generated has different file permissions that the project files generated and extracted from the downloaded zip from https://code.quarkus.io/.

Permissions from project files generated from vscode-quarkus:

Permissions from project files downloaded from https://code.quarkus.io/ as a zip, then extracted:

Most notably, the project files generated from vscode-quarkus does not have execute permissions for the maven wrapper files.

This is because when vscode-quarkus extracts the downloaded project zip, the file stream writer that is responsible for writing the extracted files onto the disk will revoke execute permissions by default.

One possible solution would be to tell the writer to give certain permissions to all files being written:

const options = {
  path: <DESTINATION PATH>,
  getWriter: (pathObject) => {
    return Writer({ path: pathObject.path, mode: 0755});
  }
};

request(<ENDPOINT URL>).pipe(unzipper.Extract(options));

This code snippet results in these permissions:

This gives 755 permissions to all files being written, including files located in subdirectories, which might not be desired.