More explicit instructions regarding gradle setup for STS/eclipse would be nice

[jholmes-pivotal]

Readme's suggest running 'gradle eclipse' and 'then import the project into your IDE and run the above classes". However, suprisingly even with STS, gradle support is not installed by default, so you just get a bunch of files that STS can't build. Instead you must first install gradle integration as described below, then import as Gradle project, and everything works as expected:
https://github.com/spring-projects/eclipse-integration-gradle/blob/master/README.md

[aclement]

Maybe I don't understand all the nuances with this particular code but if you run the gradle eclipse step on the command line then that should create the eclipse .project/.classpath files for the project and you then import the projects into STS as 'existing projects'. It isn't necessary to have the gradle tools installed in eclipse. If you did have them installed then you could skip that external gradle eclipse step and use 'import as gradle project' directly in STS.

[jholmes-pivotal]

In my case, when I did an import existing project after running gradle
eclipse on command line, the imported project(s) wasn't buildable. For
example, I could uncheck 'Project/Build Automatically' but the Build All or
Build Project options were still greyed out, and searching for a Java type
yielded nothing. I didn't see it being recognized as a Java project and
building automatically after import. Tried it a few times, but same result.
You're seeing it recognized as Java project and built correctly?

On Wed, Oct 30, 2013 at 12:22 PM, Andy Clement notifications@github.comwrote:

Maybe I don't understand all the nuances with this particular code but if
you run the gradle eclipse step on the command line then that should
create the eclipse .project/.classpath files for the project and you then
import the projects into STS as 'existing projects'. It isn't necessary to
have the gradle tools installed in eclipse. If you did have them installed
then you could skip that external gradle eclipse step and use 'import as
gradle project' directly in STS.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-27430226
.

Jeff Holmes
Senior Field Engineer, Pivotal
jholmes@gopivotal.com
503-740-2568

[wxlund]

I've had the same problem before but can't remember how I worked around it. I'm going to spend time on it later today and tomorrow.

On Oct 30, 2013, at 2:49 PM, jholmes-pivotal notifications@github.com wrote:

In my case, when I did an import existing project after running gradle
eclipse on command line, the imported project(s) wasn't buildable. For
example, I could uncheck 'Project/Build Automatically' but the Build All or
Build Project options were still greyed out, and searching for a Java type
yielded nothing. I didn't see it being recognized as a Java project and
building automatically after import. Tried it a few times, but same result.
You're seeing it recognized as Java project and built correctly?

On Wed, Oct 30, 2013 at 12:22 PM, Andy Clement notifications@github.comwrote:

Maybe I don't understand all the nuances with this particular code but if
you run the gradle eclipse step on the command line then that should
create the eclipse .project/.classpath files for the project and you then
import the projects into STS as 'existing projects'. It isn't necessary to
have the gradle tools installed in eclipse. If you did have them installed
then you could skip that external gradle eclipse step and use 'import as
gradle project' directly in STS.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-27430226
.

Jeff Holmes
Senior Field Engineer, Pivotal
jholmes@gopivotal.com
503-740-2568
—
Reply to this email directly or view it on GitHub.

[arghya88]

I am getting"could not find or load main class files"......What is the classpath that need to set up to run them.