# Unable to run example with gredale

**URL:** <https://community.stardog.com/t/unable-to-run-example-with-gredale/631>\
**Category:** Support\
**Created:** [October 3, 2017, 6:39pm UTC](https://community.stardog.com/t/unable-to-run-example-with-gredale/631 "2017-10-03T18:39:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)\
**Post date:** [October 3, 2017, 6:53pm UTC](https://community.stardog.com/t/unable-to-run-example-with-gredale/631/2 "2017-10-03T18:53:40Z")

</div>

As mentioned in [your other thread](https://community.stardog.com/t/unable-to-execute-stardog-example/584/10) about this issue, this seems to be a problem with ALL versions of Gradle in windows 10. There are some discussion threads [here](https://discuss.gradle.org/t/filename-too-long-in-windows/9222/10) and [here](https://discuss.gradle.org/t/javaexec-fails-for-long-classpaths-on-windows/15266) on [gradle.org](http://gradle.org) with some potential workarounds, and it doesn't seem like there is an actual fix in Gradle core as of yet, as evidenced by the open issues on their Github (like [this one](https://github.com/gradle/gradle/issues/1959) and [this one](https://github.com/gradle/gradle/issues/1989)).

---

_[View the full topic](https://community.stardog.com/t/unable-to-run-example-with-gredale/631)._