Ok, I figured that out. The way you refer to the task while setting
the 'dependsOn' is incorrect:
{code}
//correct: you're actually creating an empty task here:
jar.dependsOn task(':foo:bar')
//correct: you refer to an existing task
jar.dependsOn ':foo:bar'
{code}
However, you have actually found a bug :) Gradle should throw an
exception saying that you cannot add ':api:pricing:copyDataSource'
task because it already exists. See docs on the task method:
http://gradle.org/current/docs/dsl/org.gradle.api.Project.html#org.gradle.api.Project:task(java.lang.String)
I'll update the jira ticket accordingly.
Cheers!
On Sat, Jun 11, 2011 at 12:05 AM, StormeHawke
<[email protected]> wrote:
>
> Spencer Allain wrote:
>>
>> I missed the part about it only saying "skipping" task because it has no
>> actions. If you see SKIPPED instead of UP-TO-DATE, that can happen
>> because there are no inputs or outputs.
>>
> It says "UP-TO-DATE" in the output, but says in the info logging that it
> skipped due to no actions. The main logging should probably indicate
> SKIPPED rather than UP-TO-DATE in this situation
>
>
> Spencer Allain wrote:
>>
>> I think there is some legitimate bug you've encountered. The from/into
>> fields are the inputs/outputs that are clearly specified at configuration
>> time in your example, so I'm surprised the workaround doesn't work.
>>
> I filed a bug report, see the message immediately prior to the first one you
> replied to.
>
> --
> View this message in context:
> http://gradle.1045684.n5.nabble.com/Command-line-P-property-not-propagating-to-dependencies-tp4459390p4477422.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
>
>
>
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
