That workaround no longer works in the latest version of gradle when the task is being skipped because it sees no inputs or outputs prior to task execution time.
If might be possible to specify some input/output at configuration time (even if it doesn't exist) and then you can probably still use the above workaround. -Spencer --- On Fri, 6/10/11, StormeHawke <[email protected]> wrote: From: StormeHawke <[email protected]> Subject: [gradle-user] Re: Bug or feature? To: [email protected] Date: Friday, June 10, 2011, 11:02 AM Szczepan Faber wrote: > > Can you create a jira ticket and attach this repeatable test case? > http://issues.gradle.org/browse/GRADLE-1605 Szczepan Faber wrote: > > As a workaround you can use outputs.upToDateWhen { false } in your task. > Adding that to the task had no effect - I still get > :api:pricing:copyDataSource > Skipping task ':api:pricing:copyDataSource' as it has no actions. > :api:pricing:copyDataSource UP-TO-DATE > -- View this message in context: http://gradle.1045684.n5.nabble.com/Command-line-P-property-not-propagating-to-dependencies-tp4459390p4476451.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
