Leo Mekenkamp wrote:
>
> Is there a reason why there is no distinction between the separator
> between
> two project names and the separator between a project name and a task
> name?
> They both are ":".
>
I guess it's a matter of style. Java uses the same separator for packages,
types, and methods, although one could argue that the capitalization makes
it easier to tell them apart.
Leo Mekenkamp wrote:
>
> This example does not function properly when used in in a sub project.
>
It depends. It will work if there is just one global release task, or if
that task is always involved in a release. This is a common setup.
Leo Mekenkamp wrote:
>
> For sub projects one needs to (for instance) prepend getPath() like this:
>
If taskGraph.hasTask() doesn't suit your needs, you can always do
taskGraph.allTasks.any { it.project == project && it.name == "release" }
or something similar.
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer & Consultant, Gradleware
http://www.gradleware.com
Creator, Spock Framework
http://spockframework.org
--
View this message in context:
http://gradle.1045684.n5.nabble.com/task-naming-issue-tp4387343p4387413.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
