Re: [gradle-user] Re: "Cascading" tasks

[Thor Kummer]

Thanks for your reply, but it doesn't work: 08:06:10-tk@tk:~/workspace/com.one.crm>  gradle :b-one-crm:babel:jar FAILURE: Could not determine which tasks to execute. * What went wrong: Task 'jar' not found in project ':b-one-crm:babel'. * Try: Run gradle tasks to get a list of available tasks. BUILD FAILED Total time: 9.99 secs The jar tasks in the sub-projects of babel are not executed. Regards Thor Den 15-08-2011 08:14, Johan Stuyts skrev: Does that mean the you have to be in the directory of the 'b-one- crm:babel' project and run the 'jar' task from there (with out the path prefix). No, see below. Out of inteterest, it would seem like an uncessessary limitation and detract a bit from the otherwise powerful gradle command-line: E.g. instead of gradle a:b:c:jar d:e:deploy you need cd a/b/c gradle jar cd ../../../d/e gradle deploy You are using relative paths above, but you can also specify absolute paths by prefixing the relative ones with a colon. This will do what you want: gradle :a:b:c:jar :d:e:deploy -- Regards, Johan --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email