Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a chapter about Running or debugging gradle under Eclipse #880

Closed
wants to merge 1 commit into from
Closed

Add a chapter about Running or debugging gradle under Eclipse #880

wants to merge 1 commit into from

Conversation

zosrothko
Copy link
Contributor

@zosrothko zosrothko commented Nov 17, 2016

Any of the checked boxes below indicate that I took action:

For all non-trivial changes that modify the behavior or public API:

  • Before submitting a pull request, I started a discussion on the Gradle developer list,
    the forum or can reference a JIRA issue.
  • I considered writing a design document. A design document can be
    brief but explains the use case or problem you are trying to solve,
    touches on the planned implementation approach as well as the test cases
    that verify the behavior. Optimally, design documents should be submitted
    as a separate pull request. Samples
    can be found in the Gradle GitHub repository. Please let us know if you need help with
    creating the design document. We are happy to help!
  • The pull request contains an appropriate level of unit and integration
    test coverage to verify the behavior. Before submitting the pull request
    I ran a build on your local machine via the command
    ./gradlew quickCheck <impacted-subproject>:check.
  • The pull request updates the Gradle documentation like user guide,
    DSL reference and Javadocs where applicable.

Add a chapter about Running or debugging gradle under Eclipse. Fix typo for invoking gradlew.bat under Windows.

Add a chapter about Running or debugging gradle under Eclipse. Fix typo for invoking gradlew.bat under Windows.

You can generate the Eclipse projects by running
```
./gradlew eclipse # *nix-based systems
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you found this to work in practice? My understanding was that this doesn't currently do the right thing for the gradle/gradle build.

Copy link
Contributor Author

@zosrothko zosrothko Dec 10, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you are right. Running/Debugging the gradle build itself under Eclipse does not work, but this works for all others builds. This allows to degug gradle itself.

@eriwen
Copy link
Contributor

eriwen commented Nov 17, 2016

@zosrothko Thank you. The content looks good except that I want to confirm with you that ./gradlew eclipse works. Once you confirm that works on gradle/gradle I'll merge this.

@zosrothko
Copy link
Contributor Author

Yes, both

./gradlew eclipse     // on *nix
gradlew eclipse       // on windows

are working

@eriwen
Copy link
Contributor

eriwen commented Dec 16, 2016

Merged with 02097f7 — thank you @zosrothko!

@eriwen eriwen closed this Dec 16, 2016
@eriwen eriwen mentioned this pull request Dec 16, 2016
3 tasks
@zosrothko zosrothko deleted the patch-1 branch December 17, 2016 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants