Github user pdxrunner commented on the pull request:
https://github.com/apache/incubator-geode/pull/82#issuecomment-176913037
You're correct. I should have changed "./gradlew" to just "gradle" for the
.txt and .md files I updated. I also agree that gradlew, not gradle, is the
correct usage in Dockerfile.
The problem here with using gradlew is that it's not part of the release
distributions. As part of the source distro we shouldn't be calling out a
script that's not part of the package. I realize that this conflicts with the
common usage when building from a clone of the github repo. Any suggestion for
handling this disconnect between building from source distro vs. repo clone? I
favor making the text instructions consistent with the release.
Should we go back to Anthony's suggestion in GEODE-826 to use the gradlew
script from bigtop which I understand could be included in the GEODE source
distro.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
