[GRADLE-1550] A few minor typos in the documentation... Created: 16/May/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Improvement
Reporter: Brett L Schuchert Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

http://www.gradle.org/more_about_tasks.html#sec:adding_dependencies_to_tasks

1: Broken Example
build.gradle
project(':projectA')

{ task hello }

task hello

println tasks.getByPath('hello').path
println tasks.getByPath(':hello').path
println tasks.getByPath('projectA:hello').path
println tasks.getByPath(':projectA:hello').path
Output of gradle -q hello
> gradle -q hello
:hello
:hello
:projectA:hello
:projectA:hello

My output is:
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/schuchert/src/jjj/build.gradle' line: 1

* What went wrong:
A problem occurred evaluating root project 'jjj'.
Cause: Project with path ':projectA' could not be found in root project 'jjj'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Here is the gradle.build - though I just copied it from the site after typing it by hand seemed to fail:
project(':projectA') { task hello }

task hello

println tasks.getByPath('hello').path
println tasks.getByPath(':hello').path
println tasks.getByPath('projectA:hello').path
println tasks.getByPath(':projectA:hello').path

To make this work, I just found out, you must have a settings.gradle (no directory, apparently):
include 'projectA'

---------------------------------------------------------------------------------------------
2: Typo?
...o additional configuration methods. Gradle's build-in tasks...

Replace build-in with built-in

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:58:22 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.