Hi, I'm currently working on IVY-628, thinking also about IVY-399 in the mean time, and I'm struggling with the root cache location being able to be defined in almost any call to Ivy. Most tasks have a cache attribute (undocumented, but existing since very first versions of Ivy) and so do all major services methods (like resolve, publish, ...).
Do you see any interest in this, and do you think this is something used. Since it is not documented I guess users couldn't complain about this "functionality" removal. And now that we can use multiple settings, a user really wanting to use a different cache location for a particular task could simply use a different settings for that (and with settings import, you can import your regular settings and just change the defaultCache). So, do anyone see any objection to remove this facility, and rely only on cache management as defined in the settings? Xavier -- View this message in context: http://www.nabble.com/Cache-root-on-tasks-tf4899614.html#a14033823 Sent from the ivy-dev mailing list archive at Nabble.com.
