Hi Dmitriy, On 30/09/2011, at 4:34 PM, tseredz wrote:
> I'm trying to store results in a set of properties or an object from the > execution of one Gradle task so I can then pass these results into another > task. In other words, I'm trying to work with Gradle tasks as with methods > where a method can have a return value of an Object, and a calling method > can then get hold of that return value. > > I don't know if this is an advisable approach or not, but I'm not finding > much information on that in the Gradle's user guide. The only information I > find is Gradle tasks have inputs and outputs, but these are handled via > directories and files, and I don't want to go through this kind of setup for > what appears to be an easy thing I'm trying to accomplish. > > Does anyone have any ideas on this? That's generally not the kind of thing that you do in Gradle, but that's not saying it's not a good way to solve your problem. Are you able to give some more information about what your tasks do and what you are trying to achieve? That will help to get to the best solution. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
