Hmm... I think copyDatasource should not be reporting UP-TO-DATE if you delete the output. I built a tiny project with similar setup and I couldn't reproduce this problem. What gradle version do you use? Can you try to reproduce it with a smaller example so that we can attach it to a jira ticket?
Cheers! On Wed, Jun 8, 2011 at 9:21 AM, StormeHawke <[email protected]> wrote: > > Szczepan Faber wrote: >> >> Do you mean the ':api:pricing:copyDatasource' or >> ':api:copyDatasource'? If the latter then we're talking about >> different tasks and it simply may just be up-to-date. >> > :api:pricing:copyDatasource is a dependency of :api:pricing:jar, which is in > turn a dependency of :app:IQ:war. It is definitely not up-to-date, as it > reports "up-to-date" even if i delete the target file prior to running the > war target on :app:IQ. For some reason, the dependency > :api:pricing:copyDatasource is reporting UP-TO-DATE without actually doing > anything; however if I run :api:pricing:jar (or just run the copyDatasource > task directly) it works as expected > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Command-line-P-property-not-propagating-to-dependencies-tp4459390p4468070.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
