Affects Version/s: 1.0-milestone-9
Fix Version/s: None
Some dependencies are reported unresolved although they are present in the Gradle cache. If using "--refresh dependencies", the dependencies are resolved, although they are not fetched from the repository (Atrifactory) as can be seen by looking at the file date.
If the command is reissued without "--refresh dependencies", it fails again. this does not concern all dependencies, only some of them
Using version 1.0-milestone-8 produces the same result, but for fewer dependencies.
This has began suddenly, and does not happen on all our computers. It happens sometimes, and sometimes, deleting the cache solves the problem, sometimes not.
Using "--refresh dependencies" could be a workaround although not for us because we are using Eclipse Gradle import, with no possibility to use parameters.
|Field||Original Value||New Value|
|Workflow||jira with pivotal tracker [ 15487 ]||jira with pivotal tracker (no resolved, only closed) [ 18543 ]|
|Workflow||jira with pivotal tracker (no resolved, only closed) [ 18543 ]||Copy of jira with pivotal tracker (no closed, only resolved) [ 21147 ]|