On 13/09/2012, at 5:35 PM, Hans Dockter wrote:

> Just curious. One strong use case for remembering that a module was missing 
> was to speed up the IDE tasks, e.g. when there are no src or javadoc jars. 
> How would solving http://issues.gradle.org/browse/GRADLE-2455 affect that?

There are 2 levels of caching: module and artefact. We're planning to change 
how the module caching works, but not the artefact caching. So, if the module 
exists in a repository, nothing changes, whether the module has source or 
javadocs or not. If the module does not exist in any repository, the IDE tasks, 
and resolves in general, will be slower because we will go and check for a 
pom.xml, ivy.xml or jar. In return, you get an better chance of finding 
something.


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply via email to