[
https://issues.apache.org/jira/browse/CB-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088107#comment-15088107
]
Billy Catherall commented on CB-10201:
--------------------------------------
It is as easy as that, if your SDK didn't correctly set the permissions of the
source gradlew file (which we've seen happen on several different machines).
As it works now it copies the gradlew with it's existing permissions, even if
those permissions don't include execute. Then fails to build. It does show a
pretty obvious error that the gradlew file doesn't have execute permission, but
figuring out that you need to change the permission on the gradlew file in the
SDK is not so obvious. Setting the gradlew file +x after copying is a sure way
to make sure it can run, even if something didn't set the one in the SDK
correctly.
> Cordova-android not setting execute permissions on gradlew
> ----------------------------------------------------------
>
> Key: CB-10201
> URL: https://issues.apache.org/jira/browse/CB-10201
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 5.0.0
> Environment: OSX
> Reporter: Billy Catherall
> Priority: Minor
> Labels: newbie, triaged
>
> When cordova build copies the gradlew script into the platform directory it
> doesn't set the +x flag so the script throws a permissions error during build.
> ERROR building one of the platforms: Error: /xxx/platforms/android/gradlew:
> Command failed with exit code EACCES
> This can be fixed in bin/templates/cordova/lib/builders/GradleBuilder.js bu
> adding 'shell.chmod('u+x', path.join(self.root, 'gradlew'));' just after
> 'shell.cp(path.join(wrapperDir, 'gradlew'), self.root);' around line 150.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
