> The jar task is not missing because I can run it if I give the aboslut
> path.
>
> gradle :b-one-crm:babel:ejb:imp:jar
> for examle. But for some reason gradle isn't reaching it.
Gradle is not propagating tasks that are qualified with a relative or absolute
path. So "b-one-crm:babel:jar" and ":b-one-crm:babel:jar" do not propagate
"jar" to the subprojects of "babel". Absolute unqualified task names (e.g.
":jar") are not propagated either (just tested on a local project), which seems
logical, so ":b-one-crm:babel:jar" not working is consistent with that behavior.
Peter already answered your question about the propagation behavior for tasks
qualified with a relative path: only a task name (e.g. "jar") will cascade; a
task path (e.g. "b-one-crm:babel:jar") won't. The example from the tutorial you
quote also specifies an unqualified task name on the command line.
--
Regards, Johan
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
